What you’ll learn
- How SSO controls workspace entry through your identity provider
- How default and custom roles define what teammates can do
- How groups and Knowledge Base permissions define what teammates can see
- How Connector availability and approval policies limit access to external systems
- How global instructions, analytics, alerts, limits, and audit logs support responsible use
Put it into practice
1
Plan access
Decide who needs to use shared resources, who needs to build them, and who
should manage organization settings. Use default or custom roles to match
those responsibilities.
2
Organize visibility
Create groups for teams or functions, then share the right Agents,
Workflows, Knowledge Base collections, and meetings with each group.
3
Set shared guardrails
Configure global instructions for behavior that should apply to every Agent
and Workflow. Review organization Connector
availability, role privileges, and minimum approval requirements before
enabling external actions.
4
Monitor usage
Review credit usage, meeting hours, and Knowledge Base storage. Add
organization alerts or per-user limits where your team needs them.
5
Review audit logs
When you need to know who viewed or changed a resource, open organization
audit logs. Filter by person, event, or ID, and
export matching events for investigations.
Related learning
Set up SSO
Connect Cassidy to your identity provider.
Assign roles and groups
Configure privileges and shared resource visibility.
Configure global instructions
Apply organization-wide rules to Agents and Workflows.
Govern Connectors
Control external app availability, access, and action approvals.
Monitor workspace usage
Understand how your organization uses Cassidy.
Set credit alerts and limits
Track organization usage and set per-user caps.
View organization audit logs
Search who viewed or changed resources in your organization.
Choose the right Cassidy tool
Compare Agents, Workflows, and Skills.