Users & audiences
The people your assistant has met, what it has learned about each, and how to govern them as groups rather than one at a time.
When a signed-in person talks to your assistant, they appear here. This page is three things at once: a roster of who those people are, a record of what the assistant has learned about each of them, and the place where you group people so a rule can be written once rather than repeated.
Who appears here
People your own application has identified to Syncanix. A visitor who is not signed in has no identity for you to govern, so they are not on this list — though the assistant may still recognize them across visits under a name that is not an account.
One person’s page
Opening someone gives you four things:
- A short written summary of who they are and what they have been doing, with links to the exact conversations behind every claim in it.
- Their conversations over a time range you choose.
- One row per capability, showing what this person can actually do right now, why, and the control that changes it.
- What the always-on compliance scan found in their conversations — counts and severities only, never transcript content.
What the assistant remembers
If you turn learning on, the assistant keeps a short profile of each signed-in person — the preferences and context that make a second conversation better than a first. It is deliberately narrow, and every part of it is yours to inspect and delete.
- Only for people your application has identified. Nothing is learned about an anonymous visitor under an account identity.
- It runs to a monthly spending cap you set. When the cap is reached, existing profiles keep working and new learning pauses until the next month.
- Idle profiles are deleted automatically after a number of days you choose, and each person holds at most a fixed number of learned facts.
- You can erase everything learned about one person, or a group of them, in one action. It removes learned facts, overrides and group memberships — and deliberately leaves their conversations alone, because those are governed separately.
Audiences
An audience is a named group of people. Once one exists you can aim a persona at it, add guidance for it, or block capabilities for it — writing the rule once instead of per person.
- Matched by rules
- Conditions on the attributes you already record — a plan, a role, a signup date. Membership is recalculated as those change, so the group stays right without anybody maintaining it.
- Frozen into a list
- A snapshot of who matched at one moment. Useful for aiming something at a named set of people — and for that reason a fixed audience cannot carry blocked capabilities, because a frozen list of who may not do something goes stale silently.
- Targeting or governing
- Some audiences can only be targeted, not used to block things — the page says which and why on the audience itself. An audience already in use somewhere cannot be deleted until nothing references it.
Which rule wins
When several settings could apply to one person and one capability, the first match wins, in this order: internal capabilities are hidden; then anything the workspace has not enabled; then a Deny you set on this person; then a block from an audience they are in — which your explicit Allow cancels; then anything that needs approval; then it is allowed. Each row on a person’s page tells you which of these decided it.