-
Notifications
You must be signed in to change notification settings - Fork 3.9k
[No QA] Update Verify-a-Domain.md #77168
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
5ee56c2
Update Verify-a-Domain.md
clarajones-expensify 22c7e85
Rename Verify-a-Domain.md to Claim-and-Verify-a-Domain.md
clarajones-expensify 469d9f5
Update Claim-and-Verify-a-Domain.md
clarajones-expensify 395eebc
Update redirects.csv
clarajones-expensify b60e844
Update Claim-and-Verify-a-Domain.md
clarajones-expensify 2b79825
Update Claim-and-Verify-a-Domain.md
clarajones-expensify File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
66 changes: 66 additions & 0 deletions
66
docs/articles/new-expensify/workspaces/Claim-and-Verify-a-Domain.md
This file contains hidden or 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,66 @@ | ||
| --- | ||
| title: Claim and Verify a Domain | ||
| description: Learn how to claim and verify a private domain in New Expensify to enable SAML login and unlock enhanced security features. | ||
| keywords: [New Expensify, claim domain, verify domain, private domain, domain settings, enhanced security, SAML, domain admin] | ||
| --- | ||
|
|
||
| <div id="new-expensify" markdown="1"> | ||
|
|
||
| If you have a private domain (e.g., yourcompany.com), you can claim and verify it in Expensify to manage employee permissions and enable additional security features. | ||
|
|
||
| # What you can do with a claimed and verified domain | ||
|
|
||
| Once you've claimed and verified a domain, you can: | ||
| - Configure SAML login | ||
| - Enforce SAML login for domain members | ||
|
|
||
| # Step 1: Claim Your Domain | ||
|
|
||
| To claim a private domain, you must: | ||
| - Be logged in with an email address from that domain | ||
| - Have verified your contact method with a magic code | ||
|
|
||
| ## Steps to claim your domain | ||
| 1. From the left-hand menu, go to **Workspaces > Domains**. | ||
| 2. Click the Enable button. | ||
|
clarajones-expensify marked this conversation as resolved.
|
||
| a. If you have already claimed one or more domains, click the **New** button in the upper-right hand corner > **New domain** to add a new domain. | ||
| 3. Enter the name of your private domain (e.g., `yourcompany.com`) in the form. | ||
| 4. Click **Continue**. | ||
|
|
||
|
|
||
| # Where to find domain settings | ||
|
|
||
| From the left-hand menu, select **Workspaces > Domains**. | ||
|
|
||
| If you haven't claimed a domain yet, you'll see a section labeled **Enhanced security** explaining the benefits of domain control. Once domains are claimed, the **Enhanced security** section is relabeled as **Domains**. | ||
|
|
||
| Each domain is listed in its own row, showing: | ||
| - Domain name | ||
| - Verification status (Verified, Not verified) | ||
| - Overflow menu with management options | ||
|
|
||
|
|
||
| ## What happens next? | ||
|
|
||
| Depending on your email setup: | ||
|
|
||
| - **If you're not using an email from that domain**: You'll see an error. You can't claim domains that don't match your email address.. | ||
| - **If your email is from that domain but not verified**: You’ll be prompted to verify your login using a magic code. | ||
|
clarajones-expensify marked this conversation as resolved.
|
||
| - **If the domain is already claimed**: You’ll need to coordinate with an existing admin to request that your role be updated to Domain Admin. | ||
|
|
||
|
clarajones-expensify marked this conversation as resolved.
|
||
| After the domain is successfully claimed, the domain will appear under **Workspaces > Domains** in the **Not verified** state. | ||
|
|
||
|
clarajones-expensify marked this conversation as resolved.
clarajones-expensify marked this conversation as resolved.
|
||
|
|
||
| # Step 2: Verify Your Domain | ||
|
|
||
| To unlock advanced security settings and enable SAML, the domain must be verified through a DNS record. | ||
|
|
||
| ## Steps to verify your domain | ||
|
|
||
| **Note**: This process may be managed by your IT department or web consultant. | ||
| 1. Log in to your DNS service provider (e.g., Namecheap, GoDaddy, Amazon Route 53). | ||
| 2. Locate the DNS Records page (sometimes labeled as DNS Management or Zone File Editor). | ||
| 3. Add a TXT record with the verification value provided in Expensify under **Workspaces > Domains > three-dot menu > Verify domain**. | ||
| 4. Save your changes. | ||
|
|
||
| Once verified, you’ll see a confirmation message and your domain will be marked as **Verified**. | ||
This file was deleted.
Oops, something went wrong.
This file contains hidden or 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
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.