Organisations and workspaces
An organisation is your company’s account in Waridex. It holds workspaces, and everything your tests use lives in a workspace: its inboxes and their mail, its API keys, its pinned patterns, its statistics and its plan. A team that tests several products, or keeps staging apart from production, gives each its own workspace.
The first time you sign in to the dashboard, Waridex creates your organisation, with you as its Owner, and a first workspace on the Free plan. An organisation holds one Free workspace; the plans are described in tiers, quotas and retention.
Members and organisation roles
Section titled “Members and organisation roles”People join an organisation by invitation, and each member has one organisation role:
| Role | What it allows |
|---|---|
| Owner | Everything an Admin can do. There is one Owner, the person who created the organisation; ownership can be transferred to another member. |
| Admin | Every workspace of the organisation, as a workspace Admin; inviting, changing and removing members; creating workspaces; renaming the organisation. |
| Member | Only the workspaces an Admin or the Owner assigned, with the workspace role of each assignment. |
Members are never counted or charged for: an organisation has as many as it needs.
Workspace roles
Section titled “Workspace roles”A Member’s access to a workspace is one of three roles, each a fixed set of the scopes API keys use too:
| Role | Scopes |
|---|---|
| Viewer | email:read: read inboxes, messages, patterns and statistics |
| Member | email:read, email:delete, email:inject, inbox:create, inbox:delete, pattern:manage and authenticator:use, with the reserved email:reply beside them, so the role needs no change when replies ship |
| Admin | every scope of the workspace, managing its API keys and renaming it included |
A Viewer holds neither email:inject nor authenticator:use: its access stays read-only, and reading an
authenticator’s code is signing in as the enrolled user.
The dashboard hides what a role does not allow, and the API refuses it regardless with
403 scope.missing.
Invitations
Section titled “Invitations”An Admin or the Owner invites someone by email address, with an organisation role and, for a Member, the workspaces and roles to assign. The dashboard shows the invitation link once; Waridex sends no email, so the inviter passes the link on. The link is valid for seven days and works only for a person who signs in with the invited address.
A member can leave an organisation, and an Admin or the Owner can remove any member but the Owner. A change to a member’s role or assignments applies from their next request.