At the highest level, Superblocks is structured around the concept of organizations. Each organization can consist of several projects (repositories with smart contracts) and people. This helps users have an overview of all the projects linked to their organization and who has access.

If you are involved with projects in several organizations, such as a consultancy working with different clients, then you will easily be able to see and jump between all organizations in a single view.

When you log in for the first time and create a project, Superblocks will automatically create an organization for you. You can chose to do the following in an organization:

  • Projects: Create a new project, or filter for existing projects.
  • People: Invite or remove people from the organization. Manage their access roles.
  • Settings: Rename or delete the organization (your organization's URL does not change when you rename your organization).

Role-based access control

In each organization you can invite people and provide them with different levels of access. For the time being there are two defined roles:

  • Member: Has the ability to create new projects, view and manage builds.
  • Owner: All of the above. Also has full administrative access, including the ability to define other people's access, invite or remove members, delete projects, and delete the entire organization.

Superblocks uses its own role-based access control system rather than relying on 3rd party setups such as GitHub. This is to make it easier in the future to add roles for more non-technical team members with business or legal backgrounds that might benefit from interacting with certain features in the platform (e.g. smart contract monitoring).

Did this answer your question?