Team & Roles management
Renta uses a Role-Based Access Control (RBAC) model to manage user access and security. This system allows you to collaborate on data pipelines within isolated environments called Workspaces.
Workspaces
A Workspace is the fundamental unit of isolation in Renta. It functions as a secure container for your data infrastructure.
Isolation model
Every workspace operates as a completely independent environment. Resources created in one workspace are not visible or accessible from another.
-
Data isolation. Sources, Destinations, and Pipelines exist only within their parent workspace.
-
Billing isolation. Each workspace has its own subscription plan and billing settings.
-
User isolation. User access is granted per workspace. Being an Owner in "Workspace A" does not grant access to "Workspace B".
Data residency
When creating a workspace, you must select a Data Processing Location. This setting determines the physical location of the cloud infrastructure processing your data.
Immutable Setting: The Data Processing Location is permanent. You cannot change the region after the workspace is created. To change regions, you must create a new workspace and migrate your pipelines.
-
Europe (EU). Compliant with GDPR requirements. Data remains within the EU.
-
United States (US). Optimized for US-based data sources and destinations.
Roles and permissions
Renta has two roles: Owner and Member. Owners manage the workspace and its team. Members work with sources, destinations, and pipelines, and an Owner can give them permissions for the context layer.
Permission matrix
The following table details the specific capabilities of each role.
| Capability | Owner | Member |
|---|---|---|
| Workspace administration | ||
| Edit workspace settings (name, slug) | ✅ | ❌ |
| Buy, change, or cancel the subscription | ✅ | ❌ |
| View the plan and invoices | ✅ | ✅ |
| Team management | ||
| View members, invitations, and groups | ✅ | ✅ |
| Invite new members | ✅ | ❌ |
| Revoke pending invitations | ✅ | ✅ |
| Change member roles and permissions | ✅ | ❌ |
| Remove other members | ✅ | ❌ |
| Leave the workspace | ✅ (if another Owner remains) | ✅ |
| Create, edit, and delete groups | ✅ | ❌ |
| Data operations | ||
| Create, edit, and delete sources | ✅ | ✅ |
| Create, edit, and delete destinations | ✅ | ✅ |
| Create, edit, and delete pipelines | ✅ | ✅ |
| View pipeline logs and metrics | ✅ | ✅ |
| Context layer models | ||
| Open Context layers and query models through AI agents and the Renta API | ✅ | With Read context layer models, for models shared with them |
| Create models and run SQL previews | ✅ | With Manage context layer models |
| Edit and delete models | ✅ | With Manage context layer models, for models shared with them |
| Change who can access a model | ✅ | ❌ |
| Run custom SQL on a warehouse source through AI agents and the Renta API | ✅ | With Run custom queries |
| Developer resources | ||
| Create, view, and revoke API keys | ✅ | ✅ |
| Create invite links | ✅ | ✅ |
Role definitions
The following table provides a breakdown of each role's capabilities and typical use cases.
Owner
The Owner role is effectively a "Workspace Administrator". Owners have unrestricted access to all aspects of the workspace.
-
Primary responsibility. Infrastructure management, billing, and team security.
-
Best practice. Assign this role to Team Leads, DevOps Engineers, and Project Managers. maintain at least two Owners for redundancy.
Member
The Member role is designed for daily operations. Members build and maintain data pipelines. They cannot change workspace settings, the subscription, roles, permissions, or groups.
-
Primary responsibility. Building and monitoring data pipelines.
-
Best practice. Assign this role to Data Engineers, Analysts, and Developers.
Managing access
Managing team members involves inviting new users, updating roles as responsibilities change, and revoking access when necessary.
Invite a new team member
Grant workspace access to a colleague.
In the left sidebar, click your profile at the bottom, and then click Teammates. On the Team members tab, click Add member.

In the Add member sidebar, enter the email address and choose the role in Member role. For a Member, select the permissions they need in Context layer permissions. See Permissions.

Click Invite member. If the person already has a Renta account, Renta adds them to the workspace at once and emails them. Otherwise, they get an email with a link to join and appear in Invited members until they accept.
Permissions
Permissions let a Member work with the context layer. Members have none by default. Owners have all of them.
| Permission | What it allows |
|---|---|
| Read context layer models | Open Context layers and query the models shared with the member through AI agents and the Renta API. You share a model on its Access tab. |
| Manage context layer models | Create, edit, and delete models and run SQL previews. Includes Read context layer models. |
| Run custom queries | Run their own read-only SQL on the workspace warehouse sources through AI agents and the Renta API. Each query counts against the source query limit. Granted on its own: it includes nothing and no other permission includes it. |
To grant a permission:
- In the left sidebar, click your profile at the bottom, and then click Teammates.
- In Workspace members, click the member to open the Edit member sidebar.
- In Context layer permissions, select the permissions.
- Click Save. The change applies at once.

You can also select permissions when you add a member, or grant them to a group.
A permission from a group shows via group next to it, and you can't clear it in Edit member. To take it away from one person, remove them from the group.
Modifying roles
You can promote a Member to Owner or demote an Owner to Member at any time.
- In the left sidebar, click your profile at the bottom, and then click Teammates.
- In Workspace members, click the member to open the Edit member sidebar.
- In the Member role section, choose the new role.
- Click Save. The change applies at once.
A workspace always keeps at least one Owner, so the only Owner cannot switch to Member. Owners hold every permission, so you don't set permissions for them.
Revoking access
To remove a user from the workspace:
- In the left sidebar, click your profile at the bottom, and then click Teammates.
- In Workspace members, click the member to open the Edit member sidebar.
- Scroll down to the Remove member section.
- Click Remove member.
Leaving the workspace: Members can remove themselves from the workspace at any time but cannot remove other users. To leave, follow the same steps above for your own user profile.

Ownership Requirement: A workspace must always have at least one Owner. You cannot remove the last Owner or leave the workspace if you are the only Owner. To leave, first assign the Owner role to another member.
Removing a member does not delete the sources, destinations, and pipelines they created. These stay active in the workspace. Renta removes the person from every group and drops their permissions and their direct access to context layer models.
Best practices
Follow these recommendations to maintain a secure and efficient workspace environment.
Security & governance
-
Principle of least privilege. Default to the Member role for all new users. Only grant Owner privileges to users who explicitly need to manage billing or access.
-
Audit regularity. Review your Team members list quarterly. Revoke access for employees who have changed teams or left the company.
-
Service accounts. For API integrations, avoid using personal user accounts. Create a dedicated email alias (such as
etl-bot@company.com) and invite it as a Member to generate API keys.
Environment strategy
Use multiple workspaces to implement a safe software development lifecycle (SDLC) for your data infrastructure.
-
Development workspace. For testing new sources and pipeline configurations. Grant simplified Owner access to developers here.
-
Production workspace. For live business data. Restrict Owner access strictly to Senior DevOps or Team Leads. Lock down permissions to ensure stability.
Ready to get started?
Build your data pipeline today or get a personalized demo. Start free!
Need help?
Get expert support to ensure your project succeeds. We're here to help!
Feature requests?
Help shape our product! Share your ideas for new features and integrations.