Help Center
Team & Permissions
Invite members, assign roles, control access, and keep sensitive feedback governed.
What this guide helps you do
Give people enough access to do their work while protecting sensitive survey data and admin settings.
Before you start
- List who needs access.
- Decide what each person needs to do.
- Identify sensitive surveys or workspaces.
What you will do
- Map accountability
- Invite using least privilege
- Scope sensitive forms
- Collaborate safely
- Monitor activity hygiene
You are done when
- Members are invited.
- Roles follow least privilege.
- Owners know when access should be reviewed.
Overview
Permissions govern who can design surveys, open raw responses, alter Smart Data Layers, trigger distribution batches, manage billing, or push exports. Combine workspace separation with role tiers (owner, manager, editor, viewer) plus optional eligible-user lists per form when programs demand tighter guardrails.
When to use this feature
Step-by-step guide
Map accountability
Translate RACI charts into workspace roles and document which personas may touch quotas, integrations, AI models, or SPSS-ready exports.
Invite using least privilege
Default to analysts or viewers when possible; escalate editor access only until the pilot ends.
Scope sensitive forms
Leverage eligible-user assignments so only nominated operators edit distribution programs or quotas for regulated trackers.
Collaborate safely
Use threaded comments plus @mentions on surveys or results pages to capture methodological decisions next to artifacts.
Monitor activity hygiene
Review centralized activity logs whenever webhook secrets rotate or dashboards inadvertently expose identifiable fields.
Operational trust
Healthy permission posture shortens onboarding, audits, and breach investigations alike.
Screens / UI explanation
Notification pathways should honor regional calendars and bilingual templates.
Eligible-user workflows are common in healthcare, banking, telecom, or government procurements.
Best practices
Quarterly recertify rosters referenced in SOC2 or ISO evidence packs.
Maintain at least two break-glass owners but avoid dozens of unrestricted owners.
Link support tickets to collaboration threads referencing integration IDs when automations misbehave.
Tips
Export permission matrices before mergers ingest external survey inventories.
Map IdP SSO groups directly to Sentink workspace roles wherever federation exists.
Common issues
Comment mentions accidentally include personal inboxes.
Disable free-form domains; require SSO-validated identities for mentions routed outside the firewall.
Eligible-user roster drifts after reorgs.
Schedule HRIS-driven access reviews or quarterly CSV reconciliations.
FAQ
Can clients collaborate without raw response access?
Yes—grant report-only roles or embed filtered dashboards built from approved Smart Data Layers.