Skip to content

Commit

Permalink
update
Browse files Browse the repository at this point in the history
Signed-off-by: Lee Calcote <[email protected]>
  • Loading branch information
leecalcote committed Nov 3, 2023
1 parent 6b2ed07 commit d2357d0
Show file tree
Hide file tree
Showing 6 changed files with 24 additions and 26 deletions.
2 changes: 1 addition & 1 deletion content/en/cloud/catalog/_index.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
title: Catalog
weight: 2
weight: 4
description: >
The Cloud Catalog is a web-based, public catalog to facilitate easy sharing and discovery of common cloud native architectures and design patterns.
---
Expand Down
7 changes: 5 additions & 2 deletions content/en/cloud/concepts/_index.md
Original file line number Diff line number Diff line change
@@ -1,10 +1,13 @@
<!-- ---
---
title: Concepts
weight: 2
description: >
What does your user need to understand about your project in order to use it - or potentially contribute to it?
An overview of Layer5 Cloud concepts and their relationships to one another.
---

{{< figure src="concepts-overview.svg" class="image-center-shadow" >}}

<!--
{{% pageinfo %}}
Page under construction.
{{% /pageinfo %}}
Expand Down
1 change: 1 addition & 0 deletions content/en/cloud/concepts/concepts-overview.svg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
23 changes: 1 addition & 22 deletions content/en/cloud/identity/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,25 +5,4 @@ description: >
date: 2023-10-30
weight: 3
categories: [Identity]
---

{{% pageinfo %}}
Organizations, Teams, Users
{{% /pageinfo %}}

### User Accounts

Every person who uses Layer5 Cloud signs into a user account. Your user account is your identity on Layer5 Cloud and has a username and profile. For example, see Five's profile.

{{< alert type="warning" title="TODO" >}}Insert Five's user profile here.{{< /alert >}}

Your user account can own resources such as workspaces, designs, connections, credentials, tokens, Any time you take any action on Layer5 Cloud such as creating a design or reviewing a deployment request, the action is attributed to your user account.

Each user account is subscribed to a plan: Free, Team, or Enterprise. All user accounts can own an unlimited number of public and private workspaces, with an unlimited number of collaborators on those workspaces. If you use Layer5 Free, private workspaces owned by your user account have a limited feature set. You can upgrade to Layer5 Enterprise to get a full feature set for private workspaces. For more information, see [Layer5 subscription plans](https://layer5.io/pricing).

Teams allow you to organize users into groups and conveniently assign access to workspaces or to assign roles with associated keychains and keys to control permissions. For more information, see [Teams](/cloud/identity/teams).

Organizations are the basic unit of multi-tenancy inside of Layer5 Cloud.

Organizations may have any number of teams and teams may have any number of users. User accounts are treated as sovereign entities that are owned by individual individuals, not by corporations.

---
2 changes: 1 addition & 1 deletion content/en/cloud/identity/teams/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,6 @@ tags: [teams]
Organizations, Teams, Users
{{% /pageinfo %}}

Organizations can have any number of teams. Teams can have any number of users. Users can belong to any number of teams. Users may belong to any number of organizations.
Organizations are the basic unit of multi-tenancy inside of Layer5 Cloud. Organizations can have any number of teams. Teams can have any number of users. Users can belong to any number of teams. Users may belong to any number of organizations.

Outside of grouping users together, teams offer control access to workspaces and to workspace resources such as environments and managed and unmanaged connections.
15 changes: 15 additions & 0 deletions content/en/cloud/identity/users/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,21 @@ tags: [users]
Page under construction.
{{% /pageinfo %}}

### User Accounts

Every person who uses Layer5 Cloud signs into a user account. Your user account is your identity on Layer5 Cloud and has a username and profile. For example, see Five's profile.

<!-- {{< alert type="warning" title="TODO" >}}Insert Five's user profile here.{{< /alert >}} -->

Your user account can own resources such as workspaces, designs, connections, credentials, tokens, Any time you take any action on Layer5 Cloud such as creating a design or reviewing a deployment request, the action is attributed to your user account.

Each user account is subscribed to a plan: Free, Team, or Enterprise. All user accounts can own an unlimited number of public and private workspaces, with an unlimited number of collaborators on those workspaces. If you use Layer5 Free, private workspaces owned by your user account have a limited feature set. You can upgrade to Layer5 Enterprise to get a full feature set for private workspaces. For more information, see [Layer5 subscription plans](https://layer5.io/pricing).

Teams allow you to organize users into groups and conveniently assign access to workspaces or to assign roles with associated keychains and keys to control permissions. For more information, see [Teams](/cloud/identity/teams).

Organizations may have any number of teams and teams may have any number of users. User accounts are treated as sovereign entities that are owned by individual individuals, not by corporations.


Organization and teams may have any number of users accounts. User accounts are treated as sovereign entities that are owned by individual individuals, not by corporations.

Users and their tokens may be authorized to access resources. Users can be created and managed by the Provider Admins, Organization Admins, or Team Admins. Users of one organization may be granted access to resources (e.g. Workspaces and Designs) of another organization. User entitlement, roles and permissions are org-scoped, meaning that the entitlements and permissions that a given user has in one organization does not necessarily reflect the same level of access that their membership in another oganziation does.

0 comments on commit d2357d0

Please sign in to comment.