Access Control
Granting per-project interview access to org members.
Interview access is controlled at the project level. Even when the feature is enabled org-wide, no one can run an interview on a project until a project or org admin explicitly grants them access via Project Settings → Interview.
Only org members can be granted interview access. External users or unauthenticated visitors cannot run interviews regardless of access settings.
Granting access
Open the project in the Rensei web app.
Navigate to Project Settings → Interview (in the left sidebar under the project name).
Click Add access.
Search for org members by name or email. You can grant access to individual members or to a team role.
Click Grant. Access takes effect immediately.
Who can grant access
| Role | Can grant interview access |
|---|---|
| Org admin | Yes - for any project in the org |
| Project admin | Yes - for that project only |
| Project manager | No |
| Project member | No |
Project admins and org admins share the access panel. A project admin cannot revoke access granted by an org admin.
Access levels
The Interview access panel has a single level of access: Can interview. There is no read-only or reviewer mode - a grantee can start, pause, resume, and submit interviews on the project. They cannot modify configuration settings (those require org admin access).
Viewing current grants
The Project Settings → Interview access table shows all current grantees:
| Column | Description |
|---|---|
| Member | The org member's name and email |
| Granted by | The admin who granted access |
| Granted at | Timestamp of the grant |
| Actions | Revoke button (admins only) |
Revoking access
Click Revoke next to a member in the access table. Access is removed immediately. Any in-progress interviews by that member are allowed to complete; they will not be able to start a new interview on the project after revocation.
Team roles
You can grant access to all members of a team role at once. When a team role is granted:
- All current members of that role receive access.
- New members added to the role after the grant also receive access automatically.
- Removing a member from the role revokes their interview access for this project.
This is the recommended pattern for larger organizations where the set of stakeholders who run interviews changes frequently.
Interview pages are protected
The interview URL (/[orgSlug]/[projectSlug]/interview) checks access on every load. If an authenticated org member who has not been granted access navigates to the URL:
- The page renders a "You don't have interview access for this project" message.
- The message includes a prompt to contact the project admin.
- No interview data is visible.
Non-authenticated requests redirect to the login page.
Relationship to feature gate
Access control and the feature gate are independent:
Feature gate (screen_interview) | Per-project access grant | Result |
|---|---|---|
| Off | Any | Interview page shows upgrade prompt |
| On | Not granted | Interview page shows "no access" message |
| On | Granted | Interview loads and participant can run |
Both conditions must be true for an interview to be accessible.
Related Pages
- Configuration - enabling the feature org-wide and selecting a model profile
- Overview - what interviews are and how they fit in the pipeline
- Running an Interview - the participant experience