--- title: "Members and roles: who can do what | Briks" url: https://briks.dev/docs/members-and-roles description: "Invite people by emailed link and give each one a role: Owner, Admin, Editor or Viewer. See what each role can do and how many people each plan holds." last_updated: 2026-10-08 --- # Members and roles: who can do what Each person in a workspace has a role that decides what they can change, and the plan decides how many people it holds. This page covers the four roles, inviting someone, what they see when the email arrives, and changing a role, removing someone or leaving later. Inviting people starts on the Pro plan, with no seat fees, and handing a workspace to a new Owner works on any plan. 8 minute read Checked against the studio on 8 October 2026 ## The four roles What people in a workspace differ in is their role. Roles stack: each one can do everything the role below it can, and a little more. The four roles, from Owner down to Viewer. Each role can do everything the one below it can. | Role | As the studio describes it | Usually given to | | --- | --- | --- | | Owner | Everything, including billing, owners and deleting the workspace. | The business owner, or the agency lead while a site is being built | | Admin | Manages members, settings, templates and skills, and moves projects. | A practice manager, an office manager, an agency that looks after the site | | Editor | Creates, changes and publishes projects. | Designers, marketers, anyone who asks for changes | | Viewer | Sees projects, previews and analytics, and changes nothing. | An accountant, a partner, a client who only wants to watch | ## What each role can do The invitation window has a short version of this table under **What each role can do**. The fuller one below follows the checks the studio makes before each action. | Action | Owner | Admin | Editor | Viewer | | --- | --- | --- | --- | --- | | See projects, previews and analytics | Yes | Yes | Yes | Yes | | Start projects, ask for changes and publish | Yes | Yes | Yes | No | | Undo, redo and restore versions, run A/B tests | Yes | Yes | Yes | No | | Connect or remove a custom domain | Yes | Yes | Yes | No | | Use templates and save a project as a template | Yes | Yes | Yes | No | | Edit records, secrets, scheduled tasks and webhooks | Yes | Yes | Yes | No | | Write, schedule and publish social posts | Yes | Yes | Yes | No | | Change a project's briks.live address | Yes | Yes | No | No | | Delete a project, clear its analytics, create or delete its database | Yes | Yes | No | No | | Move a project to another workspace | Yes | Yes | No | No | | Rename the workspace, manage skills, make templates public | Yes | Yes | No | No | | Hire agents and approve what they ask to do | Yes | Yes | No | No | | Connect or remove the business's social accounts | Yes | Yes | No | No | | Invite people, change roles and remove members | Yes | Yes, except Owners | No | No | | Make someone an Owner, or remove an Owner | Yes | No | No | No | | Billing and deleting the workspace | Yes | No | No | No | What each role can do in a workspace. Roles cover every project in the workspace. Good to know Anyone in the workspace can open **Billing** to see the plan and the balance. Only an Owner can choose, change or cancel the plan. More on the [Billing](https://briks.dev/docs/billing) page. Agents and their approvals are covered in [Approvals and budgets](https://briks.dev/docs/agent-approvals), and social posts in [Marketing and social posts](https://briks.dev/docs/marketing). ## How many people each plan holds | Plan | People in the workspace, you included | | --- | --- | | Free | 1 | | Starter | 1 | | Pro | 3 | | Studio | 10 | | Agency | 25 | There are no seat fees. Invitations still open count as people. Free and Starter are for the owner alone, so inviting people starts on Pro. The heading on **Members** counts members against the plan, such as 2 of 3 members, with open invitations after it. When the workspace is full, **Invite people** is greyed out and a note under the table says why, with **See what's included**, which opens the upgrade window on **Bring your team in**. Trying to invite past the limit opens the same window. Revoking an open invitation or removing someone frees a place. If a workspace moves to a plan with fewer places, everyone already in it keeps their access; only new invitations are refused. An invitation can't be accepted while the workspace has no room left. Handing a workspace over is the exception. On any plan, an Owner can invite one person as Owner even when the workspace is full; **Invite people** then stays open to them, with only **Owner** to choose. A hand-over can take one place past the plan, and only while no other invitation as Owner is open. See [Handing a site to a client](https://briks.dev/docs/handing-over-to-a-client). ## Invite someone Where 1. Workspace 2. Members 3. Invite people 1. Open Members Where: Members Choose **Members** under **Workspace** in the sidebar. You see how many members there are against what the plan holds, such as 2 of 3 members, and a table with **Member**, **Role** and **Joined**. If your role cannot invite, the page says so: "Your role is Editor. An Owner or Admin invites people and changes roles." 2. Choose Invite people Where: Members The **Invite people** window opens. It reminds you that each person gets an email with a link that works for 7 days, and only for the address it was sent to. 3. Add the addresses Where: Invite people Type or paste them into **Email addresses**, separated by commas, spaces or new lines. The hint under the box says how many more people your plan has room for. You can invite up to 20 people in one go. A mistyped address is caught before anything is sent, with a note asking you to enter each one like name@example.com. 4. Pick a role Where: Invite people Under **Role**, choose one. **Editor** is picked for you. Each choice has its one line description beside it. Admins do not see **Owner** in the list, because only an Owner can make another Owner. 5. Send it Where: Invite people Choose **Send invitation** (it reads **Invite 3 people** when there are three). The page confirms who it was sent to, and anyone who was already a member is named and skipped. Limits on invitations A workspace can send 50 invitations a day. Past that, Briks says: "This workspace has sent 50 invitations today. Try again tomorrow." One invitation can be emailed 3 times a day, sent or sent again; after that its email is not sent, and you can copy its link instead. Inviting an address that already has an open invitation renews that one rather than making a second. ## What the invited person sees The email arrives with the subject "Ana Ruiz invited you to Harbour Physio on Briks" (with your name and workspace), says which role it is for and carries a **Join Harbour Physio** link. It also tells people without an account to create one with that same email address. Joining from the link 1. Open the link Where: Invitation page A page titled **Join Harbour Physio** shows who invited which address, and as which role. 2. Sign in or create an account Where: Invitation page Someone new to Briks chooses **Create an account to join** and signs up with the invited address. They confirm their email from their inbox, and that link brings them straight back to the invitation. Someone with an account chooses **I have an account** and signs in. 3. Join or decline Where: Invitation page **Join Harbour Physio** adds them and opens the studio in that workspace. **Decline** closes the invitation, and the person who sent it can invite them again later. Good to know The link only works for the address it was sent to, so a forwarded invitation gives nobody access. If someone opens it while signed in with another address, the page says so and offers **Sign in as** the invited address or **Stay as** the current one. If the invitation has run out, been used or been withdrawn, the page says which and asks them to get a new one from you. ## Manage open invitations Invitations that have not been accepted are listed under **Invitations**, below the members, with the email, the role and a **Status** such as **Expires in 5 days** or **Expired**. Expired ones stay on the list for 30 days so you can renew them. Each row's ••• menu has three choices: - **Send again**, which emails the same link. For an expired invitation it reads **Renew and send again** and gives it another 7 days. - **Copy invitation link**, which puts the link on your clipboard so you can send it yourself. It still works for that one address only. - **Revoke**, which stops the link working at once. You can invite the person again later. Tip If Briks reports that an email could not be sent, the invitation still exists. Copy its link from **Invitations** and send it through your usual email or messaging app. ## Change a role, remove someone or leave 1. Change a role Where: Members Pick the new role in the **Role** menu on that person's row. It saves straight away and the page confirms it, for example "Sam is now an Admin." 2. Remove someone Where: Members Open the ••• menu on their row and choose **Remove from workspace**, then **Remove**. They lose access to the workspace's projects at once. Their work stays. 3. Leave yourself Where: Members Open the ••• menu on your own row and choose **Leave workspace**. The same button is in the **Danger zone** at the foot of **Settings**. You cannot leave your only workspace. Owner rules Only an Owner can make someone an Owner, change an Owner's role or remove an Owner. A workspace always keeps at least one Owner, so the last one is told: "A workspace always keeps an Owner. Make someone else an Owner first." If you step yourself down from Owner to Admin, only an Owner can make you an Owner again. A team set up A physiotherapy clinic in York with four people > The clinic's workspace is on Studio, which has room for 10 people. Priya owns the clinic and is the Owner. Tom, the practice manager, is an Admin so he can invite locum staff and rename things. A freelance marketer is an Editor: she asks for a new treatments page and publishes it. The clinic's accountant is a Viewer and looks at visitor numbers before the quarterly meeting. Nobody can delete the workspace or change the plan except Priya, and the accountant can look at anything without the risk of changing a word on the site. ### Do extra members cost anything? No. There are no seat fees. Each plan includes its people, you included: 3 on Pro, 10 on Studio and 25 on Agency. Free and Starter are for the owner alone. ### Can I give someone access to just one project? Roles cover the whole workspace. To keep a project apart, move it into a workspace of its own and invite the person there. ### The invitation email never arrived. What now? Ask them to check spam first. Then use **Send again**, or **Copy invitation link** and send it yourself. ### What happens to someone's work when I remove them? It stays in the workspace. Removing a person only takes away their access. ## Read next - [Workspaces and account **Workspaces** A workspace holds your projects, members, media, skills, plan and credits. Create one, switch between them, rename one and delete one you no longer need.](https://briks.dev/docs/workspaces) - [Workspaces and account **Handing a site to a client** There is no handover button: you hand a workspace over by making your client its Owner. A walkthrough for agencies, with plans, credits and domains covered.](https://briks.dev/docs/handing-over-to-a-client) - [Workspaces and account **Your profile and sign-in** Change your name, email and password, sign in with Google, see where you are signed in, connect Telegram, pick a theme, and delete your account for good.](https://briks.dev/docs/account) - [Workspaces and account **Billing** See your plan and credits on the Billing page, buy a plan at checkout monthly or yearly, move up or down, cancel, and find your receipts and invoices.](https://briks.dev/docs/billing) Still stuck? Write to [hello@briks.dev](mailto:hello@briks.dev) with your project's name and what you expected to see. A screenshot helps.