Permissions
Permissions allow for the management of read/write access to various features of webapp.io. Permissions can be managed for the members of your organization through the members section of organization settings. Permissions are a hierarchy of keywords separated by periods (.) using
star (*) as a wildcard.
Examples:
settings.billing.tier equates to the organziation billing tier setting
permission.
settings.* equates to all organziation settings permissions.
* equates to all permissions.
Dashboard
Access to view the organization dashboard (recent commits, custom domains, new installations, organization settings) is managed thorugh thedashboard
keyword.
Install
Access to install webapp.io on new repositories is managed through theinstall
keyword.
Repository
Access to perform actions on repositories is managed the therepo keyword.
Access to perform actions on a specific repository is managed through the
repo.<reposirory name> keyword. Repository names are lower cased and have both
spaces and periods replaced with dashes(-). For example, a repository
helloWorld/my first.program is normalized to helloWorld/my-first-program
Staging Terminal
Access to the debugging terminal of a staging server is managed through therepo.<reposirory name>.stagingterm keyword.
Repository Controls
Repository controls are managed through thecontrols keyword with the
following permissions:
repo.<reposirory name>.controls.retrythe ability to retry a runrepo.<reposirory name>.controls.cancelthe ability to cancel a runrepo.<reposirory name>.controls.buttonthe ability to click buttons defined in Layerfiles
Secrets
Access to read and write secrets is managed though thesecrets keyword.
Settings
Access to read and write organization settings are managed through thesettings keyword.
Membership
Organization membership management has the following permissions:settings.members.rolesalter member rolessettings.members.usersalter organization’s userssettings.members.users.inviteinvite users to organization
Billing
Organization billing settings have the following permissions:settings.billing.tiermanage organization billing tiersettings.billing.paymentmanage organization payment method
Groups
An organization has two role groups by default, owners and members. Owners have read/write access to all parts of the organization, members have a subset. Members start with the default permissions of:dashboardrepo.*.controls.cancelrepo.*.controls.retryrepo.*.controls.stagingterm