Skip to main content
Organization membership lets a person join the intended Firedrill organization. Machine credentials let automation act within a selected scope and capability set. A project/environment selection never widens the authority of the current credential.

​
Invite a teammate

An authorized organization owner or administrator can open Settings → Members, invite the intended email address, and select a role available to that organization. The recipient accepts the invitation and signs in to that organization. They do not need to create a separate organization for the shared work. Use the Members page to inspect current members and invitations, revoke a pending invitation, or remove access where authorized. A lost acknowledgment is not permission to send duplicate invitations; recover the existing action.

​
Automation credentials

For reports, CI, or a coding-agent integration that cannot use interactive login, create a scoped machine credential.
Run from the selected project/environment. The example grants read authority only for a day; it cannot start simulations. Choose the additional capabilities your CI workflow needs from firedrill discover --json and the CI guide. The output file contains the one-time secret. Keep it outside version control and copy its secret value into your protected automation store as FIREDRILL_TOKEN. Do not paste it into a recipe, target prompt, ordinary log, or MCP config. You can also generate and revoke credentials from Settings → Machine credentials. Review scope, capabilities, and expiry before creating one.

​
Inspect and revoke

Replace CREDENTIAL_ID with a credential from your authorized list. Listing metadata does not reveal its secret again. Revocation is separate from removing a local CLI installation or signing out of the portal. See authentication for SDK token loading and security for Tool connections.