docs: remove old pages and make sure overview pages are used (#11592)

Summary
- refreshed multiple concept, guide, SDK example, policy, and
troubleshooting pages to match the latest structure
- synchronized `apps/docs/lib/sidebar-data.ts` and
`apps/docs/redirects.json` with the new layout so navigation and URL
rewrites stay consistent

---------

Co-authored-by: Copilot <[email protected]>
Co-authored-by: fcoppede <[email protected]>
This commit is contained in:
Florian Forster
2026-02-13 19:50:54 -03:00
committed by GitHub
co-authored by Copilot fcoppede
parent 943d9e0967
commit b5d7518ad1
39 changed files with 155 additions and 918 deletions
@@ -1,29 +0,0 @@
---
title: Configure applications for your frontend and backend services and clients
sidebar_label: Applications
---
import AppType from "../../guides/manage/console/_application-types.mdx";
Applications are the entry point to your project.
[Users](./users) either login into one of your applications and interact with them directly or use one of your APIs.
All applications share the roles and authorizations of their [project](./projects).
## Supported application types
ZITADEL supports the following application types:
<AppType components={props.components} />
## Security considerations
Ensure the configuration of application settings is limited to authorized users only.
You can configure applications in the [management console](/guides/manage/console/organizations-overview).
Read about our [administrators](/concepts/structure/administrators) and [granted projects](/concepts/structure/granted_projects)
concepts.
## References
- [Configure Applications in the Management Console](../../guides/manage/console/applications-overview)
- [ZITADEL API: Applications](/reference/api/application)
@@ -4,10 +4,10 @@ title: Structure
<Cards >
<Card href="/concepts/structure/instance" title="Instance" />
<Card href="/concepts/structure/organizations" title="Organizations" />
<Card href="/concepts/structure/projects" title="Projects" />
<Card href="/concepts/structure/applications" title="Applications" />
<Card href="/concepts/structure/users" title="Users" />
<Card href="/guides/manage/console/organizations-overview" title="Organizations" />
<Card href="/guides/manage/console/projects-overview" title="Projects" />
<Card href="/guides/manage/console/applications-overview" title="Applications" />
<Card href="/guides/manage/console/users-overview" title="Users" />
<Card href="/concepts/structure/administrators" title="Administrators" />
<Card href="/concepts/structure/policies" title="Policies" />
</Cards>
@@ -1,10 +0,0 @@
---
title: ZITADEL Organizations
sidebar_label: Organizations
---
import OrgDescription from './_org_description.mdx';
<OrgDescription components={props.components} name="OrgDescription" />
More about how to configure your organization read our [organization guide](../../guides/manage/console/organizations-overview).
@@ -1,47 +0,0 @@
---
title: Projects
sidebar_label: Projects
---
import ProjectDescription from './\_project_description.mdx';
<ProjectDescription components={props.components} name="ProjectDescription" />
To learn how to set up a project read this management console guide [here](../../guides/manage/console/projects-overview).
## Applications
Applications define the different clients, that share the same roles.
At the moment we support OIDC and almost every OAuth2 client. We'll be expanding this with SAML shortly.
Go to [Applications](./applications) for more details.
## Granted Organizations
To enable another organization to use a project, the organization needs a grant to the project.
Only the selected roles will be available to the granted organization.
If you are unsure on how to structure your organizations and projects, we recommend reading the guide on [solution architecture](/concepts/architecture/solution).
The granted organization will be able to manage the authorizations of their users for the granted project by themselves in their organization.
More about granted projects: [Granted Projects](./granted_projects)
## Roles
A role consists of different attributes. Only the key is relevant to the authorization and must therefore be unique.
The display name is only to provide a human-readable name if needed.
And the group should enable a better handling in ZITADEL management console, like give a user all the roles of a specific group. (Not implemented yet)
All applications in a project share the roles. Read more about roles [here](../../guides/manage/console/roles)
## Default Project
When creating a new ZITADEL instance you will find an automatically created project on the first created organization.
This default project does represent the ZITADEL project and is used to secure the different apps shipped with ZITADEL.
This includes the ZITADEL Management Console and APIs.
We do not recommend changing any settings or using this project for anything else, as this could influence the behavior of ZITADEL.
The default name of the project is "ZITADEL", this might differ on self-hosted instances, when you change the default name.
![](../../../public/img/guides/solution-scenarios/console-default-project.png)
@@ -1,81 +0,0 @@
---
title: ZITADEL Users
sidebar_label: Users
---
## Types of users
ZITADEL supports authentication and authorization for different user types.
We can mainly differentiate between Users and Service Accounts.
Users are accounts operated/used by a human, while service accounts are those operated/used by an application/third-party software.
### Users
Users typically logon with an interactive login.
This means that an application redirects a user to a website ("login page") where the user can provide the credentials.
ZITADEL handles the authentication and provides the application with a token that verifies the authentication process.
Read more on how to [login users with ZITADEL](/guides/integrate/login/login-users).
### Service accounts
Service accounts are for machine-to-machine communication, and you would use those typically to access secure backend services.
For example in ZITADEL you would require an authenticated Service Account to access the Management API.
The main difference between users and service accounts is the type of credentials that can be used for authentication: users typically logon via a login prompt, but service accounts require a non-interactive logon process.
Learn how to [use service accounts](/guides/integrate/service-accounts/authenticate-service-accounts) with ZITADEL.
### Administrators
Any user or service account can be assigned an [Administrator](/concepts/structure/administrators) role.
A user with an administrator role is not only an end-user of ZITADEL but can also manage certain aspects of ZITADEL itself.
### Federated users
Federated users are identities that are managed by a third-party identity provider.
Users can log in via an external identity provider, using [identity brokering](../features/identity-brokering) ("Single-sign-on").
Federated user [accounts are linked](../features/account-linking) to internal users to be able to assign roles and keep an audit trail.
### External users
In a multi-tenancy architecture, you might use [organizations](./organizations) to separate user groups.
By using [external user grants](../features/external-user-grant) an organization is able to invite users from another organization.
These invited users are called external users.
## Considerations
### Uniqueness of users
Users can only exist within one [organization](/guides/manage/console/organizations-overview).
It is currently not possible to move users between organizations.
User accounts are uniquely identified by their `id` or `loginname` in combination of the `organization domain` (eg, `[email protected]`).
You can use the same email address for different user accounts.
### How to structure user pools
Consider this general recommendation as a starting point:
- Create one organization ("default organization") for your own company
- Configure projects and applications in the default organization
- Structure users in organizations based on common domains that are self-managed (eg, company)
- Grant your projects to the organizations, allow Administrators to give granted roles to their users
You might want to adjust this general setup based on your [scenario](/guides/solution-scenarios).
One important consideration in the setup is that you can only have a domain once for an organization. If you have multiple teams working with the same email address, you might need to add them to one single organization that has the domain verified for the teams' domain.
For a CIAM / B2C setup, you might want to store all users in one organization and allow that organization to use a specific set of social logins.
In a multitenancy / B2B scenario, you might have thousands of smaller teams.
#### Hierarchy
There is no concept of hierarchies and inheritance based on users or organizations.
This is why we recommend to structure users along the smallest unit of groups.
You can use organization metadata or your own business logic to describe a hierarchy of organizations or user groups.
## References
- [Manage users in the Management Console](../../guides/manage/console/users-overview)
- [ZITADEL APIs: Users](/reference/api/user)
- [User onboarding and registration](/guides/integrate/onboarding)