Skip to main content
Roles & Permissions (“Manage what your team can access and do. Create custom roles to match your organisation’s needs.”) lists your permission profiles in two tables, System roles (Owner, then Admin, Sender and Viewer) and Custom roles, each row showing how many users hold the role and how many permissions it has. Owners and anyone whose role has Manage roles can open this page, and it needs a plan with Roles & permissions (Team and above, see pricing); on other plans the page offers an upgrade instead.

Video guide: Setting roles and permissions

The roles and permissions settings pageThe roles and permissions settings page

Permission profiles, and what each one allows.

Profile list and detail

Select a profile from the list to open it in the panel beside it. The panel has three tabs:
  • Permissions: the profile’s permissions, grouped into Packages, Templates, Library, Contacts, Team, Organisation, Owner powers, High-risk powers and API access. Each group shows how many of its permissions are enabled. Templates sets Template access to No access, Use or Create. Save changes counts the edits waiting to be saved, and Discard throws them away.
  • Users: the members assigned to the profile, with Manage members to change who has it on Members.
  • Details: the name, description, whether it’s built in or custom, how many users are assigned, and when it was created.

Package access

Package access, in the Packages group, sets whose packages people with the role can see:
  • Own packages: only the packages they send or that are shared with them.
  • Specific team members: their own packages plus those of the members you choose, drafts included. Pick the members in Choose team members.
  • Everyone in the workspace: every package in the workspace.
Use Specific team members when people cover for each other. For example, give two assistants a role that includes each other, and each sees the other’s packages while they’re away. Like every other role setting, changing it needs Manage roles. The Viewing as picker on the packages list and home page offers only the people the role can see. An API key that acts for members follows the access of the member it acts for. The arrow beside Save changes holds the role’s other actions:
  • Clone copies it into a new custom profile, pre-named <name> (copy). Owners only.
  • Edit details opens Edit role details, to change a custom role’s name and description.
  • Delete removes a custom role. Owners only.
Add new role, at the bottom of the list and also for owners only, opens Create permission profile, where you set a Name, an optional Description, and optionally Clone permissions from an existing profile (or None (start empty)).
The create permission profile dialog with name, description and clone-from fieldsThe create permission profile dialog with name, description and clone-from fields

Create permission profile, with an optional profile to clone from.

Under API access, Manage API keys lets a profile issue and revoke API keys in its workspace, up to the profile’s own access. No built-in role has it and built-in roles can’t be edited, so an Owner can Clone one or use Add new role, then turn it on there.

Owner powers

A custom role can hold some of the powers that are otherwise owner-only. They sit in two groups on the Permissions tab:
  • Owner powers: Manage the account (rename the organisation and change its company details), Manage branding (the logo, brand colour and how emails look on Branding) and View usage (packages, seats and activity against the plan).
  • High-risk powers: Manage roles, Invite members, Manage workspaces, Manage integrations and Manage billing. These change who can do what, or what the organisation pays, so turning one on asks you to confirm with Turn on. Everyone with the role gets it straight away.
Each power opens the matching settings page, so someone with Manage billing can open Billing, and someone with Manage workspaces can open Workspaces. Anyone who isn’t an Owner can only hand out less access than their own:
  • Permissions they don’t hold are locked, and a role they edit must have less access than theirs.
  • They can’t change a role they hold. A role they can’t change shows “You can only change roles with less access than yours”.
  • Invite members invites people into their workspace with a role that has less access than their own.
  • Manage workspaces creates workspaces, and renames, restyles and deletes the ones they belong to.
Security, closing the organisation and ownership stay with owners, and so do creating, cloning and deleting roles.
A role's Permissions tab with the Owner powers and High-risk powers groups openA role's Permissions tab with the Owner powers and High-risk powers groups open

The Owner powers and High-risk powers groups on a role's Permissions tab.

Owner

Owner is a locked, built-in role at organisation level. It can’t be edited, cloned or deleted. Workspace roles (Admin, Sender, Viewer and your custom roles) apply one workspace at a time; Owner sits above every workspace. An Owner has every permission in every workspace, owner and high-risk powers included, and sees every workspace. While someone is an Owner, their workspace role has no effect. Selecting Owner shows an Owner only group (“Can’t be given to a custom role”) above its permissions. Only an Owner can:
  • Make other members Owner, or revoke it.
  • Manage organisation security: single sign-on, verified domains, user provisioning (SCIM), session timeout, the IP allowlist and data retention.
  • Create and manage API keys that act for members.
  • Create, clone and delete roles.
  • Close the organisation’s account.
  • Sign in with a password when Require SSO is on.
Only an existing Owner can grant or revoke the role, from the member’s actions menu on Members. Each change needs confirmation and is recorded in the audit log.
An organisation must always have at least one active Owner, so the last one can’t be revoked. Keep at least two, so one person leaving never locks your organisation out. If every Owner has left, contact Flowsign support to recover access.