Roles and permissions

Every person has a role in each project: Viewer, Editor, Publisher or Admin. The role decides what they can see and change there. An admin of the project sets it from Settings > Team, can give it an end date, and can read who changed what. The people and sign-in side is in Projects, team and sign-in.

To see every role at work without building a team, the demo data of the Docker quick try adds four members (a Publisher, two Editors and a Viewer, one with an access that has ended) and two pending invitations.

The four roles

Each role includes everything the one before it can do.

  • Viewer reads. They see the project, its zones, tale groups and tales, and the analytics. They change nothing.
  • Editor works on content. They create and edit tale groups and tales and save drafts, but cannot make anything live.
  • Publisher makes content live. They publish what editors saved, set visibility and schedules, and manage zones and their displays.
  • Admin runs the project. They also reveal and rotate zone keys and the site key, and manage the team: invite people, change roles, remove access.

A person can have a different role in each project: Publisher in one, Viewer in another. Projects they are not in are not shown to them at all.

What each role can do

This is the table the dashboard shows under What each role can do, and the one the API enforces on every project request. A dash means the role cannot do it.

CanViewerEditorPublisherAdmin
See the project, its zones, tale groups and talesYesYesYesYes
See analyticsYesYesYesYes
Create and edit tale groups and tales, and save draftsNoYesYesYes
Publish: turn content on, set visibility and schedulesNoNoYesYes
Create and edit zones and their displaysNoNoYesYes
Reveal and rotate zone keys and the site keyNoNoNoYes
Manage the team: invite people, change roles, remove accessNoNoNoYes
The What each role can do table on the Team page: seven capabilities down the side, the columns Viewer, Editor, Publisher and Admin, a green tick where the role can do it and a dash where it cannot. A sentence per role sits below the table.
The same table in the dashboard, a real screenshot of Settings > Team. Every member of the project can see it.

Install admins

The admin of the whole install (the person who set TaleArt up, and anyone made an admin under Settings > Users) is an Admin in every project, whether or not they are listed as a member. They appear in a project's member list only when someone added them there, marked Install admin. Everyone else is a content manager, and their power comes from the role they hold in each project.

The Users page of Settings, listing five people. Dana Levi has the role Admin and the projects All projects. The others are content managers, each listed with their project and role, such as Spring Campaign: Editor, Spring Campaign: Viewer (until 12 Dec 2026) and Spring Campaign: Editor (access expired).
Settings > Users shows each person's role in every project they are in, with an end date or an expired note. A real screenshot, with example people.

Editors save drafts, publishers make them live

The split between Editor and Publisher works like an approval step. An editor can build and change tales and save the changes as a draft, which does not change what visitors see. A publisher reviews the draft and makes it live. Give people who write content the Editor role, and give the people who answer for what visitors see the Publisher role.

In Tale Studio an editor sees Ask a publisher to publish where a publisher has the publish controls, and the status line says the change is not visible yet. In a tale group, the switches that turn content on or off, and the schedule, are for publishers: an editor sees the same menu item greyed out with the reason Needs the Publisher role or higher.

Tale Studio open as an editor named Sam Cohen, with an Editor badge in the header. The toolbar reads All changes saved, Not visible: not updated yet, 1 change, and Ask a publisher to publish in place of a publish button.
Tale Studio for an Editor, a real screenshot. The change is saved as a draft and is not visible; the toolbar says to ask a publisher.

A Viewer sees the same screens in read-only form: controls that change something are off, with a note such as View only: your role cannot change this group.

A tale group opened as a Viewer. A note under the header reads View only: your role cannot change this group. The three tales are listed with their Shown or Hidden state, which a viewer cannot change.
A tale group for a Viewer, a real screenshot. The group can be read but not changed.

Manage the team, step by step

Only an Admin of the project, or an install admin, sees the controls below. Everyone else sees the member list and the roles table, read-only.

  1. Open Settings > Team.

    Pick the project in the header, then choose Settings and the Team tab. The page names the project and your own role beside it. The Members table lists each person with their Role, their Access (permanent, until a date, or expired), when they Joined, and a Remove button.
    Settings, Team tab, for the project Spring Campaign. The Members table lists Dana Levi (Admin, You, Install admin), Alex Rivera (Publisher), Sam Cohen (Editor), Kim Park (Viewer, until 12 Dec 2026) and Noa Katz (Editor, Expired, ended 25 Oct 2026). A role list, a Change button and a Remove button sit on each row, and an Add or invite button is at the top right.
    Settings > Team for an Admin, a real screenshot with example people. Kim Park's access ends on a date; Noa Katz's already has.
  2. Invite someone with a role.

    Choose Add or invite, then Create a one-time invitation link. Pick the Role: the hint under the list says what it allows and what it does not. The default is Editor. Optionally set Access ends. Choose Create link, then Copy link and send it to the person yourself: TaleArt sends no email. The link is shown once, works once, and expires after 7 days. The person opens it, signs up with a passkey, a username and password or a provider, and joins the project with the role you chose.
    The Add or invite drawer after an invitation was created. The invitation link is shown with the note Works once, until Nov 7, 2026, This link is shown only now. Below it: Joins as Editor, Access: Until 31 Jan 2027, a Copy link button and a Done button.
    The invitation link, a real screenshot. The link is a local test address; the note says it is shown only now, so copy it before choosing Done.
  3. Add an existing user.

    Someone who already has an account on this install needs no invitation. Choose Add or invite, keep Add someone who already has an account, type their Email, pick the Role, optionally set Access ends, and choose Add to project. They have access at once. If the email has no account, the answer is user_not_found: invite them instead. If they are already a member (even with expired access) it is member_exists: change their role in the table.
    The Add or invite drawer, to the project Spring Campaign. The option Add someone who already has an account is chosen, the email field holds maya.stern@example.com, the role is Publisher with a hint saying what a Publisher can and cannot do, and Access ends (optional) is empty. The buttons are Cancel and Add to project.
    Adding an existing user as a Publisher, a real screenshot with an example email. The hint under Role changes with the role chosen.
  4. Change a role.

    In the Members table, pick another role in the person's Role list. It saves at once, and takes effect on their next request: they do not need to sign in again. TaleArt will not leave a project without an Admin: see the last admin.
  5. Set an end date.

    In the person's Access cell choose Change, pick a date, and it saves. Permanent removes the limit. After the end date the person can no longer open the project, and the row is marked Expired. Their membership stays in the list, so you can give a new date to restore access. The same Access ends field is on the add and invite forms.
  6. Revoke an invitation.

    Invitations that were created and not yet used are in Pending invitations, with the role, the access end date, who invited, and when the link expires. Choose Revoke and the link stops working at once. A person who opened it before then, and finished joining, is already a member: remove them from Members instead.
    The Pending invitations table of the Team page with two rows: a Viewer with access until 31 Dec 2026 and an Editor with permanent access, both invited by Dana Levi on 31 Oct 2026, link expiring 7 Nov 2026, each with a Revoke button. The roles table starts below.
    Pending invitations, a real screenshot. Revoke ends a link before its seven days are up.
  7. Remove a member.

    Choose Remove on the person's row and confirm. They lose access to the project at once; their account stays, and so do their roles in other projects.
  8. Read the activity.

    At the bottom of the page, Activity lists the newest changes first, in words: Dana Levi changed Sam Cohen from Editor to Publisher. It records invitations created and revoked, people who joined, people added, role changes, end-date changes and removals, with the time of each. Only admins see it.
    The Activity list at the bottom of the Team page, newest first: Dana Levi created an invitation link for a Viewer and for an Editor, changed Alex Rivera and Sam Cohen between roles, and added Noa Katz as Editor, Kim Park as Viewer, Alex Rivera as Publisher and Sam Cohen as Editor, each with its date and time.
    The activity log, a real screenshot. Each line says who did what to whom, and when.

Time-limited access

Any membership or invitation can have an end date. Until that day the role works as usual. After it, the person has no access to the project, but stays in the list as Expired so an admin can extend it or remove them. The date must be in the future when it is set, and counts in UTC. An invitation's end date applies to the membership once the person joins, not to the link, which always lasts 7 days.

Add or invite: which one

Add someone who already has an accountCreate an invitation link
ForA person who has signed in to this install beforeA new person with no account yet
You giveTheir email, a role, an optional end dateA role and an optional end date; you send the link
Takes effectAt onceWhen the person opens the link and signs up
LinkNoneOne use, 7 days, shown once; revoke it from Pending invitations
If it is wronguser_not_found (no such account), member_exists (already a member)Revoke it and create another

The last admin is protected

A project always keeps at least one active Admin. Lowering the role of the last one, or removing them, is refused with last_project_admin: make another person an Admin first. An install admin is not held to this, since they are an Admin in every project anyway.

API tokens and the API

  • An API token acts with your role in each project, as it is at the time of each request, narrowed to the projects the token was given. A token never has more power than its owner: if you are a Viewer in a project, your token reads it and changes nothing there, even when it is read-write.
  • Zone keys and the site key can be revealed, issued and rotated only with the Admin role, so a token or the command-line tool needs an Admin owner for those.
  • The member, invitation and activity operations marked Dashboard only in the API reference need a signed-in dashboard session. An API token cannot add people, change roles or create invitations: it is refused with 403 forbidden. Listing members needs only the right to see the project.

What a refused action looks like

The dashboard turns off or hides what your role cannot do, and says why, for example Needs the Publisher role or higher. If a request gets through anyway, from an API token or an old page, the API answers 403 with this body, and changes nothing:

HTTP/1.1 403 Forbidden

{
  "error": {
    "code": "forbidden",
    "message": "Your role in this project does not allow this"
  }
}

Someone who is not a member of the project at all is refused the same way, and an expired membership counts as no membership.

Error codes

StatusCodeMeaning
403forbiddenYour role in the project does not allow this, or an API token called a dashboard-only operation.
404user_not_foundNo account has that email. Invite the person instead.
409member_existsThe person is already a member, expired or not. Change their role instead.
404member_not_foundThat person is not a member of the project.
404invitation_not_foundThe invitation is unknown, already used, expired or already revoked.
409last_project_adminThe change would leave the project without an active Admin.

If you used TaleArt before roles

Everyone who was a member of a project before roles existed became a Publisher there, which is the closest to what they could do. Nothing changed for them on the day. Install admins are still Admins everywhere. Review the team under Settings > Team and lower or raise roles as needed: Editor for people who should not publish, Admin for those who manage keys and people.

PersonRoleWhy
Agency contractor, for a campaignEditor, with an end dateThey build tales and save drafts, nothing goes live without a publisher, and access ends by itself when the contract does.
Marketing leadPublisherThey decide what visitors see and when, and manage zones, without handling keys or the team.
Analyst or stakeholderViewerThey read tales and analytics and cannot change anything.
Owner of the site or brandAdmin (at least two people)They manage keys and the team; a second admin means the project is never left without one.