Skip to content

DOC-1044 Smoother Auto identification #299

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

ntombing
Copy link
Contributor

@ntombing ntombing commented May 5, 2025

  • Updated the last paragraph for identification levels in the "Optional parameters" table.

  • added a link to info about bypassing identification

  • Restructured the "removing identification" section to remove ☒ Can't bypass identification

@ntombing ntombing requested a review from racene-swan May 5, 2025 16:20
Copy link

linear bot commented May 5, 2025

Copy link

netlify bot commented May 5, 2025

Deploy Preview for incomparable-tiramisu-91a96a ready!

Name Link
🔨 Latest commit fc787c9
🔍 Latest deploy log https://app.netlify.com/sites/incomparable-tiramisu-91a96a/deploys/6818e566ef5a4000082da378
😎 Deploy Preview https://deploy-preview-299--incomparable-tiramisu-91a96a.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@@ -73,7 +73,7 @@ https://oauth.swan.io/oauth2/auth?response_type=code&client_id=$YOUR_CLIENT_ID&r
| --- | --- |
| `onboardingId` | Avoids asking the customer to enter their own residence address if they provide that information during onboarding. |
| `email` | If you include the `email` parameter, it triggers an [email verification](../../../topics/accounts/memberships/index.mdx#invite) flow automatically. If you include the parameter *and* the email address, it triggers the email verification flow with the email address pre-filled. |
| `identificationLevel` | Indicate your preferred [identification level](../../../topics/users/identifications/index.mdx#levels-processes): `PVID`, `QES`, `Expert`, or `Auto`.<br /><br />If you include the `onboardingId`, or if you're trying to reengage your user to complete their identification, Swan recommends setting `Auto` as your preferred identification level. `Auto` allows Swan to direct your users to the best identification flow for their situation.<br /><br />If you use the `Auto` identification level when **inviting account members**, include the `accountMembershipId` in the authorization URL. |
| `identificationLevel` | Indicate your preferred [identification level](../../../topics/users/identifications/index.mdx#levels-processes): `PVID`, `QES`, `Expert`, or `Auto`.<br /><br />If you include the `onboardingId`, or if you're trying to reengage your user to complete their identification, Swan recommends setting `Auto` as your preferred identification level. `Auto` allows Swan to direct your users to the best identification flow for their situation.<br /><br />If your project is set to [bypass identification](../../../topics/accounts/memberships/index.mdx#remove-identification), and you use the `Auto` identification level when **inviting eligible account members**, include the `accountMembershipId` in the authorization URL to automatically skip identification. |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is quite clunky - is there a way to simplify it? Currently sitting at postgraduate level.

@@ -214,11 +214,10 @@ import UserBindingErrorOptions from './partials/_user-binding-error-list.mdx';
Verifying your account members' identity is a required step in most circumstances.
However, with a **detailed agreement with Swan**, you might be allowed to bypass identification for certain membership permissions.

Even with identification removed, only memberships with certain permissions can bypass identification.
Even with identification removed, only memberships with the following permissions can bypass it:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is quite confusing.

Are we trying to say that members with the following permissions don't have to go through this identification? i.e. you can only remove identification for users with those permissions?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants