Not sure where to start? Grab an open issue with the help-wanted label.
+ diff --git a/content/en/cloud/concepts/_index.md b/content/en/cloud/concepts/_index.md index e7de07886..1f03ae16a 100644 --- a/content/en/cloud/concepts/_index.md +++ b/content/en/cloud/concepts/_index.md @@ -1,24 +1,37 @@ --- title: Concepts weight: 2 -draft: true +draft: false description: > An overview of Layer5 Cloud concepts and their relationships. --- + + +The Layer5 Cloud provides a comprehensive suite of management tools for cloud-native infrastructure. Understanding the core entities and how they interact is essential for effectively managing your service meshes, clusters, and designs. + +## Core Entities + +The following concepts form the foundation of the Layer5 Cloud ecosystem: + +* **Workspaces:** Logical isolation boundaries for organizing team members, environments, and resources. +* **Environments:** Specific deployment targets (e.g., Development, Staging, Production) within a Workspace. +* **Designs:** Visual representations of your infrastructure patterns and service mesh configurations. +* **Catalogs:** Repositories of reusable patterns and best practices shared across the community or organization. +  - +### Next Steps +For a deeper dive into the technical implementation of these concepts, please refer to our [Architecture Documentation](/docs/architecture). \ No newline at end of file diff --git a/content/en/cloud/getting-started/_index.md b/content/en/cloud/getting-started/_index.md index 1c3eef95b..02a58de74 100644 --- a/content/en/cloud/getting-started/_index.md +++ b/content/en/cloud/getting-started/_index.md @@ -2,31 +2,46 @@ title: Getting Started description: Learn how to effectively manage your organizations, teams, users, workspaces, environments, and more. weight: 1 +draft: false --- - - - \ No newline at end of file +To verify your setup, try deploying a sample design: + +1. Navigate to the **Designs** section in the sidebar. +2. Click on **Import** and select a sample pattern from the Meshery Catalog. +3. Click **Deploy** and select your target Environment. + +--- + +### Need Help? +If you run into issues during setup, join our [Slack Community](http://slack.layer5.io) or check the [Troubleshooting Guide](/docs/troubleshooting). \ No newline at end of file diff --git a/content/en/cloud/identity/_index.md b/content/en/cloud/identity/_index.md index 919d6ab36..58f15caf4 100755 --- a/content/en/cloud/identity/_index.md +++ b/content/en/cloud/identity/_index.md @@ -4,4 +4,23 @@ description: > Organizations, Teams, Users weight: 3 categories: [Identity] ---- \ No newline at end of file +--- + +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. + +## [Organizations](organizations) +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. + +## [Teams](teams) +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. + +## [Users](users) +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—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. \ No newline at end of file diff --git a/content/en/cloud/overview/_index.md b/content/en/cloud/overview/_index.md index 3d1f89a71..17059d387 100644 --- a/content/en/cloud/overview/_index.md +++ b/content/en/cloud/overview/_index.md @@ -1,39 +1,27 @@ --- title: Overview -description: Here's where your user finds out if your project is for them. -weight: 2 -categories: [Examples, Placeholders] -tags: [test, docs] -draft: true +description: Learn how Layer5 Cloud centralizes management, visualization, and collaboration for your multi-cloud infrastructure. +weight: 1 +categories: [Reference, Cloud] +tags: [Cloud, Architecture, Governance] +draft: false --- - +* [**Identity**](/cloud/identity): Learn about Organizations, Teams, and Users. +* [**Security**](/cloud/security): Understand tokens, keychains, and permissions. \ No newline at end of file diff --git a/content/en/cloud/security/_index.md b/content/en/cloud/security/_index.md index d2eafae98..e38cd3671 100755 --- a/content/en/cloud/security/_index.md +++ b/content/en/cloud/security/_index.md @@ -1,10 +1,52 @@ --- title: Security -description: Tokens, Keychains, Keys, Roles +description: Manage identity and access through Tokens, Keychains, Keys, and RBAC Roles. weight: 4 +draft: false categories: [Security] -tags: [permissions] +tags: [permissions, identity, authentication] --- +Layer5 Cloud provides a multi-tenant security model designed to manage access across complex organizational structures. This section covers the core components of our Identity and Access Management (IAM) system. + +## Security Architecture + +The following diagram illustrates the relationship between Organizational Units, Roles, and the underlying Permissions: + + + +--- + +## 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. + +## Roles and Access Control +Access is granted through Role-Based Access Control (RBAC). Roles are assigned at different levels of the organizational hierarchy: +* **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. + +## 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](/docs/security/roles) for a complete matrix of permissions for each role. + - \ No newline at end of file