Drıftstack docs
Docs

‘requires admin role on that team’ when launching or stopping

You might be here because: “requires admin role on that team” · “Launching a profile on a team owner requires admin role on that team” · “Creating a session on a team owner requires admin role on that team” · “Destroying a session on a team owner requires admin role on that team” · “Reading agent sessions on a team owner requires admin role on that team” · “You do not have permission to perform this action” · “403 when I launch in my team’s workspace” · “I can see the team’s profiles but can’t launch them” · “can’t stop a teammate’s session” · “ask the owner to make me admin”

Short answer

In a team owner’s workspace your role is member or admin: a member can look at the owner’s saved things but cannot change them, so launching, creating and stopping sessions need admin. The owner chooses the role when inviting you. Ask the owner for the admin role, or do the work in your own account instead.

Check first

  • Which workspace are you acting in? Your own account never needs a role; the sentence only appears when you act on a team owner.
  • What does the sentence say you were doing? Creating a session, launching a profile, destroying (stopping) a session, launching an AI session and listing the AI sessions are each refused with their own sentence, all HTTP 403.
  • The desktop app shows “You do not have permission to perform this action.”; the API response carries the full sentence and, for an AI session launch, required_role: "admin".

Likely causes and fixes

  1. You are a member, not an admin. A member has read access to the owner’s saved session list and details, profiles and audit log; live session state and every write are admin-only. Fix: ask the owner for admin. A team can have any number of admins, each invited by the owner, and the owner is always admin on their own team.

  2. Listing AI sessions is the one read that needs admin. An AI session carries the transcript and live control state, so the list is not opened to read-only members, while the plain session list still works.

  3. You tried to stop someone else’s session. Destroying a session on a team owner needs admin. Fix: ask an admin or the owner to stop it.

  4. Any live operation on the owner’s session. Screen, control and state on a team owner’s session require admin.

If it still fails

If the owner’s Team page lists you as admin and the refusal continues, press Talk to a person in this chat (or open Help) and include the owner’s workspace, your account email, the exact sentence and the time. Roles are given by the owner, not by support.