Access¶
IAM in the sidebar opens Identity & Access Management. The line under the title is Manage users, roles, and permissions across your organization and projects. The page is /iam.
Invite the person to the organization first. Then add them to the project. If you cannot open IAM, the page says Access denied and Only organization owners & project owners / admins can manage members and roles.
Give a developer a place to deploy¶
- Open IAM. On Organization Members, click Invite Member.
- Enter their Email. Leave Role on Member. That is the default.
- Send a link to invite your teams by email. If Door creates the invitation and cannot send the mail, the dialog says Invitation created, but the email could not be sent. Copy the link and send it yourself. The new row sits under Pending Invitations until they accept.
- After they are in the organization, open Project Access. Select the project. Click Add Member. Search their email. The search starts after three characters.
- Set Project role to Developer, Admin, or Viewer. A new membership starts on Viewer until you change it. Add member saves it.
They can then open Door DevOps and select that project and environment. The registry stays a separate page. See Registry, for a Super Admin.
Organization roles¶
Invite Member asks for an organization role. The default is Member. The dropdown labels are Project Owner, Project Owner +, Validator, Super Admin, Billing Manager, Viewer, and Member. The page assigns the label. It does not describe which Hub button each role can press.
Project roles¶
On Project Access, the roles are Developer, Admin, and Viewer. A new membership starts on Viewer. Choose Developer for the people who deploy, Admin for the people who manage that project, and Viewer for the people who look.
A person must already be an organization member before they can be added to a project.
Organization Members¶
The card title is Organization Members. The line under it is Manage access and roles for organization members.
| Column | Meaning |
|---|---|
| Member | The member |
| The member's email | |
| Role | The organization role. Change it in the row |
| Status | Active for someone who has joined |
| Actions | Remove member |
Invite Member opens Invite members to join your organization.
| Field | What you set |
|---|---|
The address. The placeholder is name@example.com. | |
| Role | One of the organization roles above. It starts at Member. |
| Send a link to invite your teams by email. | Sends the invitation. |
If Door creates the invitation and cannot send the email, the dialog stays open. The title is Invitation created, but the email could not be sent. The line is Copy this link and send it manually to the address. Copy becomes Copied.
Deleting a member asks Are you sure? The line is Delete member and the email. Type email to confirm must match that email. Cancel closes the dialog. Delete removes the member. The button stays disabled until the typed email matches. Your own row says You cannot remove yourself. Removing the last owner says You must keep at least one organization owner (super admin).
Pending Invitations¶
Pending Invitations lists invites that have not been accepted. An empty card says No pending invitations. A personal workspace says Personal workspaces cannot have pending invitations.
The row actions are Resend and Revoke. While they run, the labels are Resending… and Revoking….
If Invite Member is replaced by a plan message, the title is Collaboration is a Team feature. The line is Upgrade your account to add members and manage permissions for your entire organization. The action can be Upgrade to Team. If Project Access is replaced, the title is Access limited.
Project Access¶
The card title is Project Access. The line under it is Manage project-level permissions and member access.
Add Member opens Add member to project. The line under the title is Project: and the project name.
| Field | What you set |
|---|---|
| Organization member email | Search the people already in the organization. The placeholder is Type at least three characters to search. While it searches, the list says Searching organization directory…. If nobody matches: No organization members match this search. Only directory members can be added. |
| Project role | Developer, Admin, or Viewer. A new member starts at Viewer. |
| Cancel | Closes the dialog. |
| Add member | Saves the membership. While it saves, the button says Saving…. A failure says Could not save. |
Edit project membership is the same dialog for someone already on the project. Email is locked. Save changes writes a new Project role.
Remove from project? asks Remove the person from the project. They will lose access defined at the project level. They stay in the organization. Cancel closes it. Remove confirms. While it runs, the button says Removing…. A failure says Could not remove member.
Registry¶
The registry is an organization setting, not a developer step. A Super Admin connects it. A developer uses the image Door already stores. The form is in Registry, for a Super Admin.
The older members write-up is Members. The console page to use is IAM.