Team roles and collection access
Understand owner, member, and guest capabilities plus private and selected-member collection behavior.
Last updated
Quire has three practical access kinds: team owner, team member, and guest.
Team owners
The team owner can manage members and guests, view workspace usage analytics when enabled, administer all team webhook subscriptions, and retain access across collection visibility boundaries. Ownership is an administrative role and should be limited to trusted operators.
Members
Active members can create and edit content available to them, connect MCP agents, and create webhooks. A member manages only webhooks they created. Every webhook event remains constrained by that member's effective resource access.
Guests
Guests enter through explicit resource sharing. They do not receive the general member administration or integration surfaces and cannot use access to one resource as a path to browse unrelated team content.
Collection rules
Collections can be team-visible, private, or limited to selected members. Private access belongs to the collection owner plus the team owner. Selected access belongs to the configured audience plus the team owner.
Rules inherit through the collection tree. A descendant is visible only if the person passes every ancestor rule. Moving a resource can therefore change its effective audience.