On this page
Members and roles
Invite people to a project and assign roles that decide what each of them can do. Roles keep sensitive actions limited to the right people.
Membership is per project. You invite a person by email, and they join the project with one or more roles. A member's roles determine which actions they may perform, from read-only access to full project administration including managing other members.
Roles come from the platform's identity system. The person who created a project owns it, and project administrators can invite members, change their roles and remove them. Review membership regularly and remove access that is no longer needed.
Key concepts
Member — A user who belongs to a project and can act in it according to their roles.
Role — A named set of permissions assigned to a member within a project.
Reader — A read-only role: can view resources but not change them.
Member (role) — A working role: can create and manage most resources in the project.
Admin — Full control of the project, including managing members and their roles.
Invitation — An email invite that adds a person to the project with a chosen role.
Before you start
- You are an administrator of (or the creator of) the project.
- The email address of the person to invite.
- A decision on which role matches their responsibilities.
Step by step
- Open members
From the project's actions menu choose View members to see everyone in the project and their roles.
Screenshot — The members list showing roles per personThe members list showing roles per person - Invite a person
Choose Invite, enter their email address and pick the role or roles to grant.
Screenshot — The invite dialog with the email field and role pickerThe invite dialog with the email field and role picker - Assign the right role
- Grant a read-only role for auditors or stakeholders.
- Grant a working role for engineers who build and manage resources.
- Reserve administrator roles for the few who manage the project and its members.
- Adjust roles later
Update a member's roles as responsibilities change, for example promoting a member to administrator or narrowing them to read-only.
- Remove access
When someone leaves the team or the project, remove them so access does not linger.
Examples
patrii project list # note the project ID patrii project invite dev@example.com \ --role member --project <project-id> patrii project members <project-id>
data "patrii_roles" "all" {}
resource "patrii_project_member" "dev" {
project_id = "<project-id>"
email = "dev@example.com"
role_ids = [for r in data.patrii_roles.all.roles : r.id if r.name == "member"]
}Limits & specifications
Typical roles, from least to most privileged:
| Role | Can do |
|---|---|
reader | View resources in the project; no changes. |
member | Create and manage most resources in the project. |
admin | Everything, including inviting members and changing their roles. |
Best practices
- Grant the least privilege that lets someone do their job.
- Keep the number of administrators small.
- Invite people to the specific project they need rather than sharing one broad project.
- Review membership on a schedule and remove stale access promptly.
- Prefer application credentials over shared logins for automation.
FAQ
Which roles are available?
Can a member belong to more than one project?
How do I stop someone from making changes without removing them?
Learn more
Everything you can do here in the console is also available through the Patrii Cloud API for automation and scripting.