DOCS / GUIDES

Understanding the pecking order (permissions)

How roles and permissions work, and how to keep the rooster from being everyone.

Intermediate12 min read
Before you beginYou need the cluck CLI, a Pollosoft account, and a coop to work in. No prior experience required. Curiosity and a mild fondness for chickens are helpful.

Overview

How roles and permissions work, and how to keep the rooster from being everyone. The whole thing takes about 12 minutes, and the commands below are the ones you will use along the way.

$ cluck flock add platform-team --role hen
$ cluck flock grant platform-team deploy:staging
$ cluck flock audit

Steps

  1. Roles. Chick can read, Hen can read and deploy, Rooster can administer. Custom roles can combine any permissions.
  2. Scopes. Permissions can be scoped to a coop, a service, or a single environment. The narrower the scope, the calmer the audit.
  3. Least privilege. Start every new hire as a Chick. Promote when they have proven they can find the feed.
  4. Audit. Use cluck flock audit to see who can do what. Anything with the rooster role gets flagged in yellow.

Commands used

Keep going

Stuck? Check the error codes, the FAQ, or the glossary.