Skip to main content
Workspaces are collaborative. Invite teammates, give them a role, and they build, run, and monitor together, within the guardrails the role allows.

​
Roles

Nora has five roles: Two axes separate the roles:
  • What they build: Developers create Flows and pipelines; Domain experts work with knowledge and review inside what already exists.
  • Operations: audit is for Owners and Managers. Managers can invite members and change roles, but removal and permission overrides are Owner-only.
Every action in the app is tied to a role check. If a button is grayed out, you’re one role short. What each role can open and do is configured in Permissions.

​
The member list

Settings → Members shows every active member with their role and join date. Change a member’s role from the dropdown on their row; remove them with the trash icon. You can’t edit your own row.

​
Inviting

At the bottom of Settings → Members, enter an email, pick a role (Developer by default), and press the [Send invite] button. If SMTP is configured, the invitation email goes out immediately. Without SMTP, the server issues a one-time invite link you can copy and share over any channel. The invite is confirmed when the invitee signs in with the same email.

​
The last Owner

A workspace must always have an Owner. When there’s only one, they can’t be removed or demoted. Add a co-Owner first.

​
Invitations that never land

Check spam first, then resend from the pending list. Pending invitations expire after 14 days; resending extends them.

​
When a member is removed

  • Flows and datasets they authored stay.
  • Their feedback stays, attributed to “former member”.
  • Their personal access tokens (issued via auth login) are revoked immediately.
Content belongs to the workspace, not to individuals.

​
Contact

For account issues unrelated to a specific member (login problems, lost workspace), email support@conscience.technology.