Skip to content
Sekential

Permissions

Everyone sees what concerns them, your customer too.

Read, Write or Admin, for a person or a group. Set on the customer, access follows their journeys, their Playbooks and their files.

Join for free

7-day free trial.

ExamplePermissionsAdd PermissionAdminInheritedWriteInheritedWriteDirectReadDirect

Access follows the customer.

Set access once on the customer record. Their journeys, Playbooks, steps and files pick it up. Each inherited line shows where it is managed.

ExampleCustomerWriteDirectJourneyWriteInheritedManaged onPlaybookWriteInheritedManaged on

Your customer sees what you share.

The Drive has an internal side for your team and an external side for the customer, in the portal. A contact reads the external files of their journey. Your Internal Outcomes stay within your teams.

ExampleInternalExternal

Your AI Teammates go through the same access.

An AI Teammate has the Member role: it sees what its permissions open to it. By default, it proposes a change and waits for your confirmation. A step given to an AI Teammate shows "Agent, to approve".

ExampleMemberAgent, to approveNovember 14ApproveCancel

Request access in one click.

With Read access, a colleague requests edit access, with a note if they wish. The document's admins receive the request, then grant or decline it.

ExampleRead-onlyRequest edit accessMessage (optional)Send requestWrite

What Permissions does

Three levels

Read to view, Write to edit and share, Admin to delete and choose the admins.

By person or by group

Access goes to a person or a group. Each person keeps their highest level.

Inherited access

Set on a customer, a journey, a Playbook or a template, it flows down to what depends on it. "Managed on" shows the source.

Access requests

With Read access, a colleague requests edit access. The admins grant or decline it.

Always an admin

Each document keeps at least one admin. Whoever creates a document is its admin.

A person's access

The record of a user or a group lists their access, direct or inherited.

On the customer side

A contact reads the External Drive of their journey. They join no group and see no Internal Outcome.

AI Teammates and keys

An AI Teammate has the Member role. An API or MCP key takes on its user's access.

Related features

Drive

You know what the customer sees, file by file.

Custom Objects

Your own objects, linked to your customers and your journeys.

Business Outcomes

What your customers bought and what your team aims for, against their target.

Questions about Permissions

What a customer contact sees
Their portal and the files in the External Drive of their journey, once the Playbook has started. The Internal Drive and your Internal Outcomes stay closed to them.
Read, Write, Admin
Read to view. Write to edit and to grant Read or Write. Admin to delete and choose the admins.
Access given to a group
Each member of the group receives it. A person who also has direct access keeps the higher of the two.
Where inherited access comes from
Each inherited line shows "Managed on" and its source. To change it, open the source.
Removing access
Delete the line. Each document keeps at least one admin: the last one can't be removed.
What an AI Teammate can do
An AI Teammate has the Member role and goes through permissions. Before writing, it waits for a confirmation, a setting that is on by default.
Workspace admins
They see and edit everything, and manage billing, integrations and AI Teammates.

Give everyone the right access from your first customer.

Join for free

7-day free trial.