Skip to content

Comments

feat(kno-10947) document tenancy strict mode and per-tenant guides#1242

Merged
scoti-knock merged 4 commits intomainfrom
sd-kno-10947-tenant-strict-mode
Jan 12, 2026
Merged

feat(kno-10947) document tenancy strict mode and per-tenant guides#1242
scoti-knock merged 4 commits intomainfrom
sd-kno-10947-tenant-strict-mode

Conversation

@scoti-knock
Copy link
Contributor

@scoti-knock scoti-knock commented Dec 19, 2025

Update guides documentation

  • Added tenancy strict mode and per-tenant guides to the Create guides page.
  • Also made minor improvements to the page such as fixing broken links, improving grammar, and shortening headers.

@linear
Copy link

linear bot commented Dec 19, 2025

@vercel
Copy link

vercel bot commented Dec 19, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Review Updated (UTC)
docs Ready Ready Preview, Comment Jan 9, 2026 10:28pm


## Tenancy strict mode

When using [audience targeting](/concepts/audiences) with guides, you may want to control how tenant membership is evaluated. Tenancy strict mode determines whether a tenant ID passed via `targetParams` must match the audience membership record for a user to see the guide.
Copy link
Contributor Author

Choose a reason for hiding this comment

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

TODO: Add screenshot of dashboard toggle to this section and include a line about where to enable the setting.

Copy link
Contributor

@thomaswhyyou thomaswhyyou left a comment

Choose a reason for hiding this comment

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

This is really great, thank you Scoti!

My dashboard PRs haven't landed yet but will update once they are available in dashboard for screenshots.

- **Global scope.** The guide renders once per user, regardless of which tenant they're currently in. This is ideal for feature announcements that users should only see once, like feature releases, general onboarding, and account-level user notifications.

- **Per-tenant scope.** The guide renders once per user-tenant pair. Users will see the guide in each tenant where they're eligible, even if they've dismissed it in another tenant. This is ideal for tenant-specific messaging like billing updates or workspace-specific onboarding.

Copy link
Contributor

Choose a reason for hiding this comment

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

I think it's worth mentioning that the global vs per-tenant scope can be configured when you create a guide but immutable once it's created?

Also wondering if we want to add a screenshot of the switch ui for this config?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes, good call on both. I'll add in the immutable note when I add screenshots 👍

Co-authored-by: Thomas <thomas.whyyou@gmail.com>
@scoti-knock scoti-knock changed the title feat(kno-10947) add tenancy strict mode docs feat(kno-10947) document tenancy strict mode and per tenant guides Jan 9, 2026
@scoti-knock scoti-knock changed the title feat(kno-10947) document tenancy strict mode and per tenant guides feat(kno-10947) document tenancy strict mode and per-tenant guides Jan 9, 2026
@scoti-knock scoti-knock merged commit 3949604 into main Jan 12, 2026
5 checks passed
@scoti-knock scoti-knock deleted the sd-kno-10947-tenant-strict-mode branch January 12, 2026 16:09
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