User Preferences¶
How per-user preferences in Contio influence the behavior of Partner API endpoints.
Overview¶
Contio users can adjust workspace and meeting defaults from the Account Preferences page in the Contio web app. A subset of those preferences shapes the behavior of Partner API requests made on behalf of that user — most visibly, the access defaults applied to a meeting at the moment it is created.
This guide documents the preferences the Partner API observes, the endpoints they influence, and what your integration can expect.
Preferences observed by the Partner API¶
| Preference | Surface | Where it applies |
|---|---|---|
| Sharing Defaults for New Meetings | Account Preferences | Meeting access on POST /v1/partner/user/meetings |
The list above is intentionally narrow — only preferences whose effects can be observed in a Partner API response are listed here.
Sharing Defaults for New Meetings¶
What the user sees¶
The Sharing Defaults for New Meetings control in Contio's Account Preferences page is a single-select with three options:
- Set my meetings to be secret by default — Meeting and recap are restricted to explicit participants only.
- Keep meeting notes secure in my workspace — The agenda link is shareable before the meeting; the recap is shared with workspace members afterwards but not with people outside the workspace.
- Share notes with guests after meetings — The agenda is shareable before the meeting and the recap is shareable afterwards, including to guests with the link.
The Partner API does not expose a read endpoint for this preference — it is internal state owned by the user, observable only through its effect on create-time meeting access.
How it shapes a newly created meeting¶
When a meeting is created via POST /v1/partner/user/meetings, the API resolves the meeting's access posture from the creating user's preference before persisting the meeting. The behavior is:
| User preference | Pre-meeting agenda visibility | Post-meeting recap visibility |
|---|---|---|
| Set my meetings to be secret by default | Explicit participants only | Explicit participants only |
| Keep meeting notes secure in my workspace | Anyone with the meeting link | Explicit participants and workspace members |
| Share notes with guests after meetings | Anyone with the meeting link | Workspace members and anyone with the link |
Implications for partner integrations¶
- The user's preference always wins on create. The create endpoint does not accept access overrides in the request body. A meeting created on behalf of a user always reflects that user's Sharing Defaults at the moment of create.
- Post-create overrides remain available. If your integration needs a meeting to land in a specific access posture regardless of the user's preference, call
PATCH /v1/partner/user/meetings/{id}immediately after the create. The API reference documents the access fields supported by the update endpoint. - Two users in the same workspace can produce different access on create. Two creates against the same workspace but on behalf of different users will follow each user's individual preference — they will not converge to a workspace-level default.
Best practices¶
- Don't assume a default. Treat the access values returned in the create response as the source of truth for that meeting; do not hardcode an assumed posture in downstream code.
- Adjust after create, not before. If your integration needs a guaranteed posture (e.g., always shareable, always private), follow the create with a PATCH rather than asking users to change their preference.
- Communicate the user-side control. If your partner app surfaces a "make this meeting secret / shareable" UI, point users at the Account Preferences page in Contio to control the default; per-meeting overrides go through your own PATCH-backed UI.
Related¶
- API Guide — Authentication, error model, and common request patterns.
PATCH /v1/partner/user/meetings/{id}— Adjust an existing meeting's access posture. See the API reference for the accepted fields.- Release Notes — Sharing Defaults enforcement on create landed in version 1.8.1.