Skip to content

Commit 75968f9

Browse files
Merge pull request #467 from kinde-oss/Fix/Minor-link-issues
Fix/minor link issues
2 parents f7cebc1 + 1db364a commit 75968f9

File tree

2 files changed

+3
-11
lines changed

2 files changed

+3
-11
lines changed

src/content/docs/build/set-up-options/self-serve-portal-for-orgs.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ title: Enable self-serve portal for orgs
44
sidebar:
55
order: 7
66
relatedArticles:
7-
- beebe908-27f8-4be6-b74c-05fc8ff5dfb5
7+
- f36bce4a-52bb-4785-865b-6b33356f9838
88
---
99

1010
You can configure a self-serve portal to enable authorized organization members to be able to self-manage functions provided by Kinde. For example, you can allow them to update their business details, payment details (if you have billing set up), multi-factor auth settings (coming soon), and manage organization members (coming soon).

src/content/docs/workflows/about-workflows/index.mdx

Lines changed: 2 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -13,17 +13,9 @@ In Kinde, workflows exist to give you (almost) unlimited power over how Kinde wo
1313

1414
Develop code in your own repo, and push it to a Kinde workflow, where we execute it in ways that you define, triggered by Kinde events.
1515

16-
Currently, you can use the following triggers:
16+
See the [Triggers](/workflows/example-workflows/workflow-user-post-auth/) section for the whole list of triggers.
1717

18-
- [user:pre_registration](/workflows/example-workflows/pre-user-registration-workflow/) - when a user attempts to register an account.
19-
- [user:post_authentication](/workflows/example-workflows/workflow-user-post-auth/) fires after the user has completed single factor authentication (e.g. email + password or Google), and before authorization.
20-
- [m2m:token_generation](/workflows/example-workflows/m2m-token-generation-workflow/) - when a request to the token endpoint is made with an M2M application.
21-
- [user:new_password_provided](/workflows/example-workflows/new-password-provided-workflow/) - when a user requests to create or reset a password.
22-
- [user:existing_password_provided](/workflows/example-workflows/existing-password-provided-workflow/) - when a user hasn’t signed in, but they have requested to sign in and given their current password.
23-
- [user:token_generation](/workflows/example-workflows/user-token-generation/) - An ID or access token is generated after authentication or refresh token request.
24-
- [user:pre_mfa](/workflows/example-workflows/pre-mfa-workflow/) - where the user has completed single factor authentication (e.g. email + password or Google) and determined which organization (if any) they are trying to access. This trigger is only available to customers on a Kinde Scale plan.
25-
26-
We will add more triggers (and allow you to create your own) as we develop the feature.
18+
We will add more (and allow you to create your own) as we develop the feature.
2719

2820
## When to use a workflow
2921

0 commit comments

Comments
 (0)