-
Notifications
You must be signed in to change notification settings - Fork 437
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
docs(legal): Account Lockout Policy (#5958)
* typo * docs(legal): account lockout policy * sidebar * remove intros * fix broken link --------- Co-authored-by: Fabi <fabienne@zitadel.com>
- Loading branch information
1 parent
c7e0d97
commit 057ac92
Showing
5 changed files
with
70 additions
and
6 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,62 @@ | ||
--- | ||
title: Account Lockout Policy | ||
custom_edit_url: null | ||
--- | ||
|
||
This policy is an annex to the [Terms of Service](../terms-of-service) that clarifies your obligations and our procedure handling requests where you can't get access to your ZITADEL Cloud services and data. This policy is applicable to situations where we, ZITADEL, need to restore your access for a otherwise available service and not in cases where the services are unavailable. | ||
|
||
## Why to do we have this policy? | ||
|
||
Users may not be able to access our services anymore due to loss of credentials or misconfiguration. | ||
In certain circumstances it might not be possible to recover the credentials through a self-service flow (eg, loss of 2FA credentials) or access the system to undo the configuration that caused the issue. | ||
These cases might require help from our support, so you can regain access to your data. | ||
|
||
We will require some initial information and conditions to be able to assist you, and will require further information to handle the request. | ||
We also keep the right to refuse any such request without providing a reason, in case you can't provide the requested information. | ||
|
||
## Scope | ||
|
||
In scope of this policy are requests to recover | ||
|
||
- ZITADEL Cloud account (customer portal) | ||
- Manager accounts to a specific instance | ||
- Undo configuration changes resulting in lockout (eg, misconfigured Action) | ||
|
||
Out of scope are requests to recover access | ||
|
||
- Where you have to option to ask another Admin/Manager | ||
- by end-users who should ask an Admin/Manager instead | ||
- self-hosted instances | ||
|
||
## Process | ||
|
||
Before you send a request to restore access to your account, please make sure that can't ask your manager/admin or another manager/admin to recover access. | ||
|
||
### ZITADEL Cloud account | ||
|
||
If you need to recover your ZITADEL Cloud account for the customer portal, please send an email to [support@zitadel.com](mailto:support@zitadel.com?subject=ZITADEL%20Cloud%20account%20lockout): | ||
|
||
- State clearly in the subject line that this is related to an account lockout for a ZITADEL Cloud account | ||
- The sender's email address must match the verified email address of the account owner | ||
- State the reason why you're not able to recover the account yourself | ||
|
||
Please allow us time to validate your request. | ||
Our support will get back to you to request additional information for verification. | ||
|
||
### Manager access to an Instance | ||
|
||
If you need to recover a Manager account to an instance, please make sure you can't recover the account via another user or service user with Manager permissions. | ||
|
||
Please visit the [support page in the customer portal](https://zitadel.cloud/admin/support): | ||
|
||
- State clearly in the subject line that this is related to an account lockout the affected instance | ||
- State the reason why you're not able to recover the account yourself | ||
|
||
Please allow us time to validate your request. | ||
Our support will get back to you to request additional information for verification. | ||
|
||
## Entry into force | ||
|
||
This policy is valid from May 31, 2023. | ||
|
||
Last revised May 31, 2023 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
057ac92
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Successfully deployed to the following URLs:
docs – ./
zitadel-docs.vercel.app
docs-git-main-zitadel.vercel.app
docs-zitadel.vercel.app