Skip to content

Commit 7e505b2

Browse files
SyedAsad108SyedAsad108
authored andcommitted
docs: add descriptive content to identity index page
Signed-off-by: SyedAsad108 <ID+username@users.noreply.github.com>
1 parent d2cc4f9 commit 7e505b2

File tree

1 file changed

+20
-1
lines changed

1 file changed

+20
-1
lines changed

content/en/cloud/identity/_index.md

Lines changed: 20 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,4 +4,23 @@ description: >
44
Organizations, Teams, Users
55
weight: 3
66
categories: [Identity]
7-
---
7+
---
8+
9+
Organizations are the basic unit of multi-tenancy inside of Layer5 Cloud. The identity structure is highly flexible: organizations can have any number of teams, teams can have any number of users, and users can belong to any number of teams and organizations.
10+
11+
Below is an overview of the core identity components within the Layer5 Cloud.
12+
13+
## [Organizations](organizations)
14+
Organizations serve as the fundamental component of multi-tenancy within the Layer5 Cloud.
15+
16+
They act as the top-level parent entity. All users and teams ultimately roll up to an organization. While Free plan users are limited to a single default organization, enterprise environments can leverage organizations to strictly isolate resources, billing, and access control across entirely different business units.
17+
18+
## [Teams](teams)
19+
Outside of grouping users together, teams offer controlled access to workspaces and to workspace resources such as environments and managed and unmanaged connections.
20+
21+
Administrators can create teams as child units below the top-level organization. This allows you to apply unique settings, permissions, and workspace access to a specific set of users without altering the parent organization's settings.
22+
23+
## [Users](users)
24+
Each user account represents an individual collaborator. Individual user accounts exist beyond the bounds of organizations.
25+
26+
Anyone who uses Layer5 Cloud signs into a user account, which acts as your sovereign identity. Your user account can independently own resources such as workspaces, designs, connections, and tokens. Any action taken on the platform—such as creating a design or reviewing a deployment request—is directly attributed to your individual user account, regardless of which teams or organizations you belong to.

0 commit comments

Comments
 (0)