You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CLAUDE.md
+42-3Lines changed: 42 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -96,7 +96,7 @@ When implementing a new API route, ask the user whether it should be part of the
96
96
3. Add the endpoint to the relevant group in the `API Reference` tab of `docs/docs.json`.
97
97
4. Regenerate the OpenAPI spec by running `yarn workspace @sourcebot/web openapi:generate`.
98
98
99
-
Route handlers should validate inputs using Zod schemas.
99
+
Route handlers should validate inputs using Zod schemas. Put coercion, defaults, minimums, maximums, and cross-field validation in the schema instead of scattering parsing logic through the handler.
For GET requests, prefer using API routes with react-query over server actions. This provides caching benefits and better control over data refetching.
Copy file name to clipboardExpand all lines: docs/docs/configuration/auth/scim.mdx
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -72,7 +72,7 @@ When a pending user signs in, Sourcebot moves them to **Active** and they count
72
72
73
73
When your identity provider deactivates a user by sending `active: false`, Sourcebot marks the user as **Suspended**. Suspended users cannot access the organization, and Sourcebot revokes their active sessions, API keys, and OAuth tokens.
74
74
75
-
If your identity provider reactivates the user by sending `active: true`, Sourcebot restores their membership. Users who had already become active return to active access; users who had never signed in return to pending.
75
+
If your identity provider reactivates the user by sending `active: true`, Sourcebot restores their membership as **Pending**. They become **Active** and billable again only after they sign in and access the organization.
76
76
77
77
78
78
## Roles
@@ -106,6 +106,6 @@ Additional attributes may be sent by your identity provider, but Sourcebot ignor
106
106
Sourcebot supports SCIM 2.0.
107
107
</Accordion>
108
108
<Accordiontitle="When do SCIM-created users become billable seats?">
109
-
SCIM-created users become billable seats after they sign in and access the organization for the first time. Until then, they appear as pending and do not count toward billing. Suspended users also do not count toward billing.
109
+
SCIM-created or reactivated users become billable seats after they sign in and access the organization. Until then, they appear as pending and do not count toward billing. Suspended users also do not count toward billing.
0 commit comments