TheArchive/zitadel
1
0
Fork 0
mirror of https://github.com/zitadel/zitadel.git synced 2025-01-06 15:18:53 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: fix typo in saas.md (#6692)

Browse Source 
* Fix typos in saas docs

Fix typo and remove gender specific pronoun

* Fixed grammar error

---------

Co-authored-by: Fabi <fabienne@zitadel.com>
Co-authored-by: Elio Bischof <elio@zitadel.com>
This commit is contained in:
Austin Turner 2023-10-11 07:05:20 -06:00 committed by GitHub
parent 2fba12d5c2
commit dad1b4db7f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/docs/guides/solution-scenarios/saas.md
View File

@ -3,7 +3,7 @@ title: Set up a SaaS Product with Authentication and Authorization using ZITADEL
sidebar_label: Software-as-a-Service
---
This is an example architecture for a typical SaaS product.
This is an example architecture for a typical SaaS product.
To illustrate it, a fictional organization and project is used.
## Example Case
@ -17,10 +17,10 @@ This means that the users and also their authorizations will be managed within Z
## Organization
An organization is the ZITADEL resource which contains users, projects, applications, policies and so on.
An organization is the ZITADEL resource which contains users, projects, applications, policies and so on.
In an organization projects and users are managed by the organization.
You need at least one organization for your own company in our case "The Timing Company".
As next step grate an organization for each of your costumers.
Your next step is to create an organization for each of your customers.
## Project
@ -39,7 +39,7 @@ You can configure `check roles on authentication` on the project, if you want to
To give a customer permissions to a project, a project grant to the customers organization is needed (search the granted organization by its domain).
It is also possible to delegate only specific roles of the project to a certain customer.
As soon as a project grant exists, the customer will see the project in the granted projects section of his organization and will be able to authorize his own users to the given project.
As soon as a project grant exists, the customer will see the project in the granted projects section of their organization and will be able to authorize their own users to the given project.
## Authorizations
@ -69,4 +69,4 @@ The last possibility is to show the private labeling of the project organization
For this the Allow User Resource Owner Setting should be set.
:::note
More about [Private Labeling](/guides/manage/customize/branding)
:::
:::