Skip to main content
PUT
Change login access
  • A member can get use, edit or manage; the whole team, use or edit. A level of null removes access.
  • No one can change the access of the login’s creator, an Owner or an Admin.
  • Removing someone’s last access stops their unfinished jobs on the login.
  • Only the Dashboard makes the change, for someone who manages the login. Elsewhere this returns a dashboard_url to the login’s Share menu.
  • Callers: an API key, an MCP OAuth token or a Dashboard session.
  • Permission: logins:manage.
  • Effect: Creates or changes something.
  • Errors: not_found, login_access_required, team_unavailable, access_fixed, grantee_not_member, team_level_not_allowed, and the errors any request can get.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

id
string
required

a saved login ID: login_ and 32 lowercase hex digits

Example:

"login_0f8e2d1c4b3a49e8a7f6e5d4c3b2a190"

Body

application/json
grantee
object
required
level
enum<string> | null
required

Null removes their access

Available options:
use,
edit,
manage

Response

On the Dashboard: who has access now; Elsewhere: the Share menu

login_id
string
required
creator
object | null
required

Who created it, and so manages it; null for a login saved before teams existed

team
enum<string> | null
required

The whole team's level, later joiners included; null when the team has none

Available options:
use,
edit
members
object[]
required

Each member's own level. Every Owner and Admin manages it whatever this lists