TheArchive/zitadel
1
0
Fork 0
mirror of https://github.com/zitadel/zitadel.git synced 2025-12-08 21:42:15 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: rename instance settings to default settings (#7484)

Browse Source 
* docs: rename instance settings to default settings

* docs: correct local reference to docs

* docs: correct local reference to docs

---------

Co-authored-by: Max Peintner <max@caos.ch>
This commit is contained in:
Fabi
2024-03-06 11:36:04 +01:00
committed by GitHub
parent 84f5b9433c
commit 258e91cf66
21 changed files with 48 additions and 47 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/docs/concepts/features/custom-domain.md
View File

@@ -10,4 +10,4 @@ By configuring a custom domain within ZITADEL, organizations can replace the def
This not only enhances the overall user experience but also reinforces the organization's brand presence. Additionally, custom domains can contribute to trust and credibility, as users are more likely to recognize and trust URLs associated with the organization rather than generic domains. Overall, ZITADEL's custom domain feature empowers organizations to tailor the authentication process to align with their brand identity and user expectations.
Learn how to [configure a custom domain in ZITADEL Cloud](/guides/manage/cloud/instances#add-custom-domain) or how to configure [custom domain when self-hosting](/self-hosting/manage/custom-domain).
Learn how to [configure a custom domain in ZITADEL Cloud](/docs/guides/manage/cloud/instances#add-custom-domain) or how to configure [custom domain when self-hosting](/docs/self-hosting/manage/custom-domain).

2
docs/docs/concepts/features/identity-brokering.md
View File

@@ -17,7 +17,7 @@ For example, if Google is configured as an identity provider in your organizatio
## How to use external identity providers in ZITADEL
Configure external identity providers on the instance level or just for one organization via the [Console](/guides/manage/console/instance-settings#identity-providers) or ZITADEL APIs.
Configure external identity providers on the instance level or just for one organization via the [Console](/guides/manage/console/default-settings#identity-providers) or ZITADEL APIs.
You will find [detailed integration guides for many Identity Providers](/guides/integrate/identity-providers) in our docs.
ZITADEL also provides templates to configure generic identity providers, which don't have templates.

2
docs/docs/concepts/structure/instance.mdx
View File

@@ -13,7 +13,7 @@ One instance normally runs on one domain and represents one issuer (e.g login.cu
One instance can contain multiple [organizations](/concepts/structure/organizations),
which in turn can represent your own company (e.g. departments), your business customers or a consumer organization.
Read more about how to configure your instance in our [instance guide](/guides/manage/console/instance-settings).
Read more about how to configure your instance in our [instance guide](/guides/manage/console/default-settings).
![Overview](/img/concepts/objects/object_overview.png)

2
docs/docs/concepts/structure/policies.md
View File

@@ -4,6 +4,6 @@ sidebar_label: Setting and Policies
---
Settings and policies are configurations of all the different parts of the instance or an organization. For all parts we have a suitable default in the instance.
The default configuration can be overridden for each organization, some policies are currently only available on the instance level. Learn more about our different policies [here](/guides/manage/console/instance-settings.mdx).
The default configuration can be overridden for each organization, some policies are currently only available on the instance level. Learn more about our different policies [here](/guides/manage/console/default-settings.mdx).
API wise, settings are often called policies. You can read the proto and swagger definitions [here](../../apis/introduction.mdx).