Approving Access Requests
When someone asks to join one of your projects, their request waits for you to review it before they can see or leave feedback. Approving requests lets you control exactly who works on a project and what they're allowed to do.
Where Pending Requests Appear
Access requests show up in two places for project owners and admins: in the project's Members area alongside your current members, and as an in-app notification when a new request comes in. Each pending request lists the person's name and email so you can recognize who is asking to join before you decide.
Deciding on a Request
Open the project and go to the Members section to see everyone waiting for approval. For each request you can either approve it and set how much access the person gets, or decline it to keep them out of the project.
Access Levels You Can Grant
The access level you pick decides what the new member can do once they're in. You can change it later from the Members section if their role changes.
Access level | What they can do |
|---|---|
Client | Leave feedback pins and notes, confirm or reopen items, and reply. Best for stakeholders reviewing the site. |
Teammate | See all comments, leave feedback, and work tickets — set status, assign owners, add labels and due dates, and reply with proof. |
Admin | Everything a teammate can do, plus act on all comments and manage members and access requests. |
Setting Comment Visibility
When you approve a request, you also decide whether the member sees only their own comments or every comment on the project. Keeping a client to their own comments avoids overwhelming them with your team's internal notes, while giving teammates the full view helps them coordinate work.
For video-based projects, you can also grant access to specific videos at approval time, so a reviewer only sees the clips they're meant to comment on.
Related topics: Members and Roles, Inviting People to a Project, Notifications.