for each organization and project, a member can have one of the following roles:

  • owner: full access to everything in organization and project resources.
  • administrator: full access to everything in organization and project resources except updating organization settings, transferring projects outside of the organization, and adding new owners.
  • developer: read-only access to organization resources and content access to project resources but cannot change any project settings.
  • read-only: read-only access to organization and project resources (available on team and enterprise plans).

when you first create an account, a default organization is created for you and you'll be assigned as the owner. any organizations you create will assign you as owner as well.

manage organization members

to invite others to collaborate, visit your organization's team settings to send an invite link to another user's email. the invite is valid for 24 hours. for project scoped roles, you may only assign a role to a single project for the user when sending the invite. you can assign roles to multiple projects after the user accepts the invite.

invites sent from a saml sso account can only be accepted by another saml sso account from the same identity provider.

viewing members via management api

you can also view organization members using the sentinelpay management api:

bash
# get your access token from dashboard settings
export SENTINEL_ACCESS_TOKEN="your-access-token"
export ORG_ID="your-organization-id"

# list organization members
curl "https://api.sentinelpay.org/v1/organizations/$ORG_ID/members" \
  -H "Authorization: Bearer $SENTINEL_ACCESS_TOKEN"

transferring ownership

each sentinelpay organization must have at least one owner. if your organization has other owners then you can relinquish ownership and leave the organization by clicking leave team in your organization's team settings.

otherwise, you'll need to invite a user as owner, and they need to accept the invitation, or promote an existing organization member to owner before you can leave the organization.

organization vs project scoped roles

project scoped roles are only available on the team and enterprise plans.

  • if a member has an organization-level role, they will have the corresponding permissions across all current and future projects within that organization.
  • if a member is assigned a project-scoped role, they will only have access to the specific projects they've been assigned to.

organization permissions table

resource action owner admin dev
organization update settings
delete org
members list members
add owner
add admin
revoke invite

project permissions table

resource action owner admin dev
project create/delete
pause/restart
api keys read keys
rotate secrets