Permissions
See https://developer.travis-ci.com/format (under @permissions) for a description of the API payloads.
The permissions that clients have on the Travis CI API are generally based on GitHub permissions.
They can also take other things into account like feature flags or the type of token used to authenticate against our API.
Permissions are currently defined under lib/travis/api/v3/permissions in the travis-api code base.
Entity type | Permission | Based on | Description and notes |
---|---|---|---|
build | cancel | pull access to repo | whether the client can cancel a build |
build | restart | pull access to repo | whether the client can restart a build |
cron | create | push access to repo | whether the client can create a cron |
cron | delete | push access to repo | whether the client can delete a cron |
env_var | delete | push access to repo | whether the client can delete an env_var |
env_var | update | push access to repo | whether the client can update an env_var |
env_vars | create | push access to repo | whether the client can create env_vars |
job | cancel | pull access to repo | whether the client can cancel a job |
job | restart | pull access to repo | whether the client can restart a job |
job | debug | push access to repo | whether the client can debug a job |
key_pair | create | push access to repo | whether the client can create a key_pair |
key_pair | delete | push access to repo | whether the client can delete a key_pair |
key_pair | update | push access to repo | whether the client can update a key_pair |
key_pair | create | push access to repo | whether the client can generate a new key_pair |
organization | sync | currently always false | whether the client can trigger a sync for an org |
repository | activate | push access to repo | whether the client can activate the repo on travis |
repository | deactivate | push access to repo | whether the client can deactivate the repo on travis |
repository | star | pull access to repo | whether the client can star the repo |
repository | unstar | pull access to repo | whether the client can unstar the repo |
repository | create_cron | push access to repo | whether the client can set up new crons for the repository |
repository | create_env_var | push access to repo | whether the client can add a new environment variable to builds for this repo |
repository | create_key_pair | push access to repo | whether the client can add a custom RSA key pair to builds for this repo |
repository | create_request | push access to repo | whether the client can trigger new builds for the repository |
user | sync | user is the same user associated with the client | whether the client can trigger a sync for a user |