-
Notifications
You must be signed in to change notification settings - Fork 175
Chore: Restructre Sidebar and Top Level Items #1008
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
PragalvaXFREZ
wants to merge
7
commits into
layer5io:master
Choose a base branch
from
PragalvaXFREZ:feat/revamp-top-sections
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
b4c1d0b
Chore: Restructre Sidebar and Top Level Items
PragalvaXFREZ 7caa657
Update references of pages to account for restructuring
CodexRaunak 1e40846
Restructure and consolidate the sections
CodexRaunak 74f12af
Merge branch 'master' into feat/revamp-top-sections
CodexRaunak 322d5d6
renaming to identity and security
PragalvaXFREZ 28304fc
add override for white background for meet-five-page cards
PragalvaXFREZ 3d5558f
oveeride background for meet five page
PragalvaXFREZ File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,75 @@ | ||
| --- | ||
| title: Identity and Security | ||
| linkTitle: Identity and Security | ||
| description: > | ||
| Organizations, teams, users, roles, keychains, keys, sessions, and tokens. | ||
| weight: 3 | ||
| categories: [Identity, Security] | ||
| tags: [permissions, identity, authentication] | ||
| aliases: | ||
| - /cloud/identity/ | ||
| - /cloud/security/ | ||
|
|
||
| --- | ||
|
|
||
| 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. | ||
|
|
||
| Below is an overview of the core identity components within the Layer5 Cloud. | ||
|
|
||
| ## Identity | ||
|
|
||
| Organizations serve as the fundamental component of multi-tenancy within the Layer5 Cloud. | ||
|
|
||
| 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. | ||
|
|
||
| Outside of grouping users together, teams offer controlled access to workspaces and to workspace resources such as environments and managed and unmanaged connections. | ||
|
|
||
| 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. | ||
|
|
||
| Each user account represents an individual collaborator. Individual user accounts exist beyond the bounds of organizations. | ||
|
|
||
| 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 is directly attributed to your individual user account, regardless of which teams or organizations you belong to. | ||
|
|
||
| ## Organizational Units | ||
|
|
||
| Layer5 Cloud uses a hierarchical structure to isolate resources and manage users at scale: | ||
|
|
||
| * **Provider Organizations:** The top-level entity that can manage multiple tenant organizations. | ||
| * **Tenant Organizations:** Individual customer or project-specific organizations (e.g., Layer5, Intel). | ||
| * **Teams:** Logical groupings of users within an organization to facilitate collaborative management. | ||
| * **Users:** Individual accounts that are members of teams and organizations. | ||
|
|
||
| ## Role and Access Control | ||
|
|
||
| Access is granted through Role-Based Access Control (RBAC). Roles are assigned at different levels of the organizational hierarchy: | ||
|
|
||
| * **Provider Administrators:** Management of provider-level settings and tenant organizations. | ||
| * **Organization Administrators:** Full control over an entire tenant organization. | ||
| * **Organization Billing Managers:** Access restricted to subscription and financial management. | ||
| * **Team Administrators:** Management of specific team resources and memberships. | ||
| * **Workspace Administrators:** Management of workspace-level resources and access. | ||
|
|
||
|  | ||
|
|
||
| ## Key Management and Tokens | ||
|
|
||
| Beyond structural roles, Layer5 Cloud uses cryptographic and session-based security: | ||
|
|
||
| ### Keychains | ||
|
|
||
| Keychains are collections of keys used to manage environment-specific access and signing. They allow for the logical grouping of related security credentials. | ||
|
|
||
| ### Keys | ||
|
|
||
| Keys are the atomic unit of access control within the system. They are used for secure communication between Meshery and Layer5 Cloud, as well as for signing design patterns. | ||
|
|
||
| ### Tokens | ||
|
|
||
| Tokens provide temporary, secure access to the platform. | ||
|
|
||
| * **Session Tokens:** Used for web browser authentication. | ||
| * **Personal Access Tokens (PATs):** Used for programmatic access via CLI or CI/CD pipelines. | ||
|
|
||
| ### Need more detail? | ||
|
|
||
| Check out the [Roles Reference](/cloud/concepts/identity-and-security/roles/) for a complete matrix of permissions for each role. |
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.