Environments and credentials

Environments

An environment is a stand of the project: Dev, Staging, Production. It has a name, an address and a Production environment flag. Environments are created by the project lead: open Credentials in the project and press New environment, or Add Dev, Staging and Production on an empty page.

A credential

A credential is one account: "admin", "Test buyer", "Stripe API". It has a name, an environment, an address, and at least one of login, password and token. A note can say things like "reset every night".

Press New credential. The dice button next to the password field generates one: random, memorable or a PIN. The login, password, token and note are stored encrypted and shown only by rights.

Who can use it

Rights on a credential never go beyond rights on the project. Inside the project a person has one of three levels:

• No access: sees the name, the environment and who manages it.
• Uses: sees the login, shows and copies the password, opens the stand.
• Manages: everything above, plus the reveal log, editing and rights.

Workspace owners and admins and the project lead always manage. By default everyone in the project uses a credential; in Who can use it you can switch to chosen people only.

Expiry and a new password

A credential can expire after a number of days from the last change of its values: handy for temporary test accounts and tokens for 90 days. An expired credential is still shown, just marked.

New password in the credential menu generates a password and saves it. Talvedo does not change the password in the system itself: copy it, change it there and save it here.

In issues

In a description or comment, type @ and pick a credential of this project. The issue gets a chip with the environment and the name, but no values: each reader sees the credential by their own rights.