Most productivity platform’s access management is designed around identity-based management. This typically means that you need to know (or gather) your community member’s email addresses, and then add their email to the tool they need access to.
We understand how this fundamentally doesn’t work in a community. Instead, Supercluster Airlock enables you to give access based on community engagement proof rather than identity. Some examples of community proof include:
Any of these proofs can be used as requirements for tooling access, removing the need for you to individually collect emails from your community members.
Existing productivity tools typically require you to grant and remove access to single emails. We’ve realized this process is both incredibly time-consuming and error prone for many communities.
Supercluster Airlock enables admins to define access levels based on their predefined groups. Remember - groups are defined by a set of requirements, not by individuals. This means that admins no longer need to worry about granting and removing access to single users (which they can still do, if needed!), but instead can easily grant and remove access for entire groups within their team, even if they do not have their member’s emails.
As a team admin, you likely have a million things you need to do, and granting access to tools should be pretty close to the bottom of that list. Existing tools require you to get your community member’s emails, and grant them access one by one.
With Supercluster Airlock, once requirements are defined for your group, access to tooling is completely self-serve by your community members. This means no more collecting emails, and no more adding or removing users single-handedly.
When your community members no longer meet the requirements defined in your group, their access to tools will be automatically removed.
Your community, like most communities, likely depend on multiple tools for document collaboration, project management, code collaboration, etc. All these tools enable your community to effectively collaborate. Unfortunately, this also means that you typically have to manage access for each individual system.
With Supercluster Airlock, each of your defined groups will be able to control access to multiple productivity tools. This means you can define your group requirements once, and use that definition across any (or all!) of your productivity tools.