Organizations & members
Everything in BlockNext belongs to an organization — workflows, credentials, API keys, runs and credits alike. Your personal account is how you sign in; the organization is what owns the work.
That ownership is deliberate. A credential you connect keeps working when you are on holiday, and a flow someone else built does not stop when they change jobs.
Members hold exactly one role, and the roles are ordered — each one can do everything the role below it can:
| Role | Can |
|---|---|
| Owner | Everything, including billing, deleting the organization, and changing anyone’s role |
| Admin | Manage members, credentials, API keys and settings |
| Editor | Build and run workflows, use credentials, see runs |
| Viewer | Read-only: look at flows and run history, change nothing |
The organization’s creator becomes its owner, and ownership cannot be assigned away by anyone else.
Inviting people
Section titled “Inviting people”Invite from Settings → Members by the identifier the person signs in with — their email address, or the account they use for an enabled social login. Once they accept, everything the organization owns is available to them at their role’s level.
Because credentials are organization-owned, adding a member gives them the use of every stored connection without ever exposing its contents: secrets are decrypted at execution time only, never shown in the UI or returned by the API. See the security model.
Switching organizations
Section titled “Switching organizations”An account can belong to several organizations, each with its own role, and the switcher in the top bar moves between them. Nothing is shared across the boundary — credentials, flows, keys and credits all stay with the organization they were created in.