Reuse analytics across customers
Suppose several customers need the same revenue definitions and sales dashboard. Mirroring lets you reuse that content while you manage each customer’s users and data access separately. You can:- Give a new customer existing domains and dashboards without rebuilding them.
- Manage metric definitions, business context, and dashboard changes in one organization.
- Let customers ask questions using a shared domain without letting them edit it.
- Choose which organizations receive each object and who can access it.
What a mirror is
A mirror is a read-only, live view of a source domain or dashboard. WisdomAI does not copy the source content. The mirror refers to the original, so it stays synchronized with it.- Customers cannot edit a mirror. You edit the original in the authoring organization.
- Mirroring does not change warehouse refresh schedules. It also does not guarantee that an open browser redraws immediately.
- You cannot mirror an existing mirror into another organization. Create each mirror from the original object.
- A mirror depends on its original. Keep the original and its organization active while customers need the mirror.
- Mirroring a dashboard does not mirror its domain. Mirror each object separately.
Where content and users belong
Use one organization for authoring the shared content and a separate private organization for each customer.
Add customer users to their customer organization. They do not need membership in the authoring organization to use its mirrors. Administrators who manage mirroring need permissions in both the source and destination organizations.
A Site Administrator creates the customer organizations. See Manage Organizations.
What customer users can do
Users in a customer organization can use mirrored content as follows:- View mirrored dashboards and load their widget data.
- Browse mirrored domains.
- Chat using mirrored domains.
Access to content and access to data
Mirroring controls access to shared content. Your data policies control which records a viewer can see. Mirrored objects follow the viewer’s permissions, not the permissions of the person who shared them. Row-level security (RLS), column-level security (CLS), and connection parameters apply according to the viewer’s own identity. Configure the viewer’s identity, row-level security, column-level security, and connection parameters as needed. An organization name or dashboard filter does not enforce access to customer records. For more on data policies, see Row-Level Access Control.What stays hidden from tenant users
Mirrored objects hide sensitive source context. Customers do not see the source’s chats or authoring metadata, such as original messages and AI workstream details, including SQL and RLS debug information.Target access
When you mirror an object, you choose who in each destination organization can access it.
A target-access change applies to every selected organization when you save. Switching a mirror to Admins only removes its all-user grant. It does not remove individual or group grants you added separately.
Limits
- The mirror dialog loads up to 100 eligible organizations. For larger rollouts, provision mirrors through the API.
- Select all organizations selects the organizations currently available. It does not include organizations created later.
- If you do not see Mirror, ask your administrator to check your permissions and whether your account has mirroring enabled.
Related articles
Set up object mirroring
Create customer organizations, add users, and mirror domains and dashboards.
Set up tenant organizations and mirrors with the API
Provision organizations, users, and mirrors with GraphQL.
Manage Organizations
Create, edit, and archive organizations as a Site Administrator.