---
title: "Academy Article"
canonical_url: "https://academy.laioutr.com/en/artikel/give-access-to-one-project-or-environment"
locale: en
meta:
"og:title": "Academy Article"
---
[Go to home](https://academy.laioutr.com/en)
- [Cockpit](https://academy.laioutr.com/en/bereiche/cockpit)
- [Team, roles and access](https://academy.laioutr.com/en/leitfaeden/team-roles-and-access)
- [Give access to a single project or environment](https://academy.laioutr.com/en/artikel/give-access-to-one-project-or-environment)
# Give access to a single project or environment
A role can be granted on a single project or a single environment instead of the whole organisation. The member then sees and reaches only that project or environment: project list, environment switcher, Studio and deployments.
## Before you start
- Plan
- All plans; environments depend on the plan
- Role
- Owner
- Duration
- 5 min
### Prerequisites
- Project with the required environments
- Suitable built-in or custom role
Last reviewed on October 15, 2026
Without a restriction, a member reaches every project in the organisation and every environment in it. For many teams that is too broad: an agency looking after one shop should not see the others, and not everyone working on dev should deploy to production.
That is why an Owner grants a role on one of three levels:
- **Organisation**: applies to all projects and environments.
- **Project**: applies to one project and all its environments.
- **Environment**: applies to one environment of a project, for example Developer on stage but not on main.
Everything else follows from that: the project list shows only permitted projects, the environment switcher only permitted environments, Studio only opens there and deployments are only possible there. An Owner never grants more rights than they hold on that level.
Members without such a restriction keep working as before. Partners serving many client organisations use partner access instead.
## Step by step
1. 1 ### Step 1: Invite the member
In the organisation settings under **Members**, add the person via **Invite** without giving them a role for the whole organisation.
2. 2 ### Step 2: Open the member profile
Click the person in the member list to open their profile in the organisation.
3. 3 ### Step 3: Choose the level
Add a role and choose a project or a single environment of that project as its scope.
4. 4 ### Step 4: Choose the role
Select a built-in role such as Developer or Content Manager or a custom role of the organisation and save.
5. 5 ### Step 5: Add further scopes
If needed, add further projects or environments with their own role, for example Developer on dev and Content Manager on main.
## Check the result
After signing in, the person sees only the granted projects in the project list. The environment switcher lists only permitted environments, and deploying to a non-granted environment is not possible.
## Frequently asked questions
Does a project role narrow an organisation role?
No. A role on the organisation level always applies to all projects. For limited access, the person gets no organisation role, only roles on projects or environments.
Who can grant project access?
An Owner, and only with actions they hold on that level themselves.
What changes for existing members?
Nothing, as long as nobody sets a scope. Members without a restriction keep working as before.
How do agencies work with several clients?
For single projects, a project role is enough. Partners with many client organisations use partner access, which reaches all connected organisations with one login.
## Related
- [Assign roles and permissions](https://academy.laioutr.com/en/artikel/assign-roles-and-permissions)6 min
Roles decide what a member can see and do in Cockpit. Besides the built-in roles Owner, Developer, Project Manager and Content Manager, the organisation defines custom roles with selected permissions under Roles and assigns them when inviting.
- [Create projects and dev and stage environments](https://academy.laioutr.com/en/artikel/create-projects-and-dev-and-stage-environments)6 min
A project is created in the organisation settings under Projects and starts with the live environment main. Further environments such as stage or dev are created in the project under Environments as a copy of an existing one.
- [Understanding the main, dev and stage environments](https://academy.laioutr.com/en/artikel/understanding-main-dev-and-stage-environments)5 min
Every project starts with the main environment, which is the live storefront. Further environments such as stage or dev run beside it as separate copies with their own address, pages, apps and deployments until their work is promoted to main.
- [Manage client organisations in the Partner Portal](https://academy.laioutr.com/en/artikel/manage-client-organisations-in-the-partner-portal)6 min
The Partner Portal lists every client organisation linked to the partner account. Partner members work in them with one login and the access the client granted, without being invited to each organisation.
- [Give the customer service team access](https://academy.laioutr.com/en/artikel/give-your-customer-service-team-access)5 min
The service team gets a role of its own with exactly the permissions it needs and is invited to the organisation with that role. Billing, API keys and deployments stay out of reach.
## Learn it in a lesson
- [Invite the team, roles and API keys](https://academy.laioutr.com/en/lektionen/go-live-team-roles-and-api-keys)8 min
## [Team, roles and access](https://academy.laioutr.com/en/leitfaeden/team-roles-and-access)
Search this guide
1. [Assign roles and permissions](https://academy.laioutr.com/en/artikel/assign-roles-and-permissions)6 min
2. [Create and manage API keys](https://academy.laioutr.com/en/artikel/create-and-manage-api-keys)6 min
3. [Give access to a single project or environment](https://academy.laioutr.com/en/artikel/give-access-to-one-project-or-environment)5 min
4. [Give the customer service team access](https://academy.laioutr.com/en/artikel/give-your-customer-service-team-access)5 min
5. [View activity and the audit log](https://academy.laioutr.com/en/artikel/view-activity-and-audit-log)5 min
## Structured Data
```json
{
"@context": "https://schema.org",
"@graph": [
{
"@id": "https://academy.laioutr.com/#website",
"@type": "WebSite",
"inLanguage": "en",
"name": "Default",
"url": "https://academy.laioutr.com/",
"translationOfWork": {
"@id": "https://academy.laioutr.com/#website"
}
},
{
"@id": "https://academy.laioutr.com/en/artikel/give-access-to-one-project-or-environment#webpage",
"name": "Academy Article",
"url": "https://academy.laioutr.com/en/artikel/give-access-to-one-project-or-environment",
"@type": [
"WebPage",
"FAQPage"
],
"breadcrumb": {
"@id": "https://academy.laioutr.com/en/artikel/give-access-to-one-project-or-environment#breadcrumb"
},
"isPartOf": {
"@id": "https://academy.laioutr.com/#website"
},
"mainEntity": [
{
"@id": "https://academy.laioutr.com/en/artikel/give-access-to-one-project-or-environment#/schema/question/1"
},
{
"@id": "https://academy.laioutr.com/en/artikel/give-access-to-one-project-or-environment#/schema/question/2"
},
{
"@id": "https://academy.laioutr.com/en/artikel/give-access-to-one-project-or-environment#/schema/question/3"
},
{
"@id": "https://academy.laioutr.com/en/artikel/give-access-to-one-project-or-environment#/schema/question/4"
}
],
"potentialAction": [
{
"@type": "ReadAction",
"target": [
"https://academy.laioutr.com/en/artikel/give-access-to-one-project-or-environment"
]
}
]
},
{
"@id": "https://academy.laioutr.com/en/artikel/give-access-to-one-project-or-environment#breadcrumb",
"@type": "BreadcrumbList",
"itemListElement": [
{
"@type": "ListItem",
"name": "Home",
"item": "https://academy.laioutr.com/en",
"position": 1
},
{
"@type": "ListItem",
"name": "Cockpit",
"item": "https://academy.laioutr.com/en/bereiche/cockpit",
"position": 2
},
{
"@type": "ListItem",
"name": "Team, roles and access",
"item": "https://academy.laioutr.com/en/leitfaeden/team-roles-and-access",
"position": 3
},
{
"@type": "ListItem",
"name": "Give access to a single project or environment",
"item": "https://academy.laioutr.com/en/artikel/give-access-to-one-project-or-environment",
"position": 4
}
]
},
{
"@id": "https://academy.laioutr.com/en/artikel/give-access-to-one-project-or-environment#/schema/question/1",
"@type": "Question",
"inLanguage": "en",
"name": "Does a project role narrow an organisation role?",
"acceptedAnswer": {
"@type": "Answer",
"text": "No. A role on the organisation level always applies to all projects. For limited access, the person gets no organisation role, only roles on projects or environments.
"
}
},
{
"@id": "https://academy.laioutr.com/en/artikel/give-access-to-one-project-or-environment#/schema/question/2",
"@type": "Question",
"inLanguage": "en",
"name": "Who can grant project access?",
"acceptedAnswer": {
"@type": "Answer",
"text": "An Owner, and only with actions they hold on that level themselves.
"
}
},
{
"@id": "https://academy.laioutr.com/en/artikel/give-access-to-one-project-or-environment#/schema/question/3",
"@type": "Question",
"inLanguage": "en",
"name": "What changes for existing members?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Nothing, as long as nobody sets a scope. Members without a restriction keep working as before.
"
}
},
{
"@id": "https://academy.laioutr.com/en/artikel/give-access-to-one-project-or-environment#/schema/question/4",
"@type": "Question",
"inLanguage": "en",
"name": "How do agencies work with several clients?",
"acceptedAnswer": {
"@type": "Answer",
"text": "For single projects, a project role is enough. Partners with many client organisations use partner access, which reaches all connected organisations with one login.
"
}
}
]
}
```