We've invented Networks Sites to enable a new breed of internet properties to exist and thrive in the next 2 decades. One of the core tenets of a Network Site is hybrid access.
Many websites and services exist in only 2 states - either they are public or they are private (or at least need signin). Lots of community sites, FB groups etc operate in this mode. Various closed spaces like Slack, MS Team, Discord, etc also operate the same way.
Introducing Hybrid Access Control
We think there's another elegant way - HybridAccess where the same system can have varying levels of access.
#HybridAccess enable endless use cases - paid memberships, paywalls, subscriber only areas where premium content may be shared, or community tech support or enabling private group discussions, cohorts and special sessions, etc.
The MainCross system is built on TOP Channels and hence a network operator can select each channel to be:
- Public - discoverable and accessible to anyone without needing to log in. This is the default.
- Restricted - discoverable by anyone, accessible to all network members
- Protected - discoverable by anyone, accessible only to channel members
- Private - not discoverable, accessible only to channel members
- Sensitive - Private with additional protection
The Network Site can be setup with a hybrid access scheme, where some channels are public, some are restricted, some are protected etc, depending on what the purpose of the Network Site is.
This allows the Network Site to have utility for various user levels - from the casual user, to a member, to a premium member, rather than being completely hidden behind a login screen or paywalled.
| Public channel | Restricted channel | Protected channel | Private channel | |
| Discovery | Open | Open | Open | None |
| Access | Public | Members | Controlled | Controlled |
Edit 10/08/23 - Further contents of this post are now deprecated and left for posterity. These help resources contain the up-to-date information at any time:
Private channels - a rather powerful feature
We've had an early version of the private channel feature out for a while. Today I'm delighted to showcase the next version of #PrivateChannels which is robust and supported by admin and user flows.
Once a channel has been create as a Private Channel, then all its resources are private and available only to members who have been explicitly put on the Access Control List (ACL).
A post from a private channel is not shimmed or hidden on the client side, as is done with many simplistic solutions out there. The access credentials are checked on the server for every resource access, and hence there is no way to bypass them.
Read more in the help article.
Access control mechanism
When encountering a resource from a Private Channel, one can request for access with a personalized note if one likes:
This request is sent to the Network Heroes for accepting (or rejecting).
See it live: https://demo1.maincross.org/topics/511/opinion/4482/1st-post-in-a-private-channel/private
Automatic access
Network heroes can generate Magic Links to automatically grant access to Private Channels. Magic Links allow seamless access by bypassing the request-grant protocol.
Dashboard
A dashboard is available to Network Heroes for:
- generate / deprecate Magic Links
- tracking the status of invitations
- accepting / rejecting requests for access
- finding all the channel members
What's next
Currently, we have 2 access control mechanisms - Request/grant protocol and automatic access. A 3rd access control mechanism will be added - Access on payment.
