Keep form work inside the right team and workspace boundaries
KinoForms gives teams role-aware product surfaces for owners, admins, members, editors, viewers, respondents, and integrations without unsupported security claims.
Form work crosses too many access boundaries
A team might need owners for tenant settings, workspace editors for form changes, reviewers for submissions, respondents for external access, and integrations with API scopes.
Access boundaries mapped to product surfaces
KinoForms keeps the product structure explicit: team roles, workspace roles, respondent access settings, and scoped integration keys each describe a different boundary.
- Team owners, admins, and members
- Workspace admins, editors, and viewers
- Respondent access settings
- API key scopes for forms and submissions
Use cases
- Agency workspaces for separate clients
- Program applications with multiple reviewers
- Internal request forms with limited editors
- Submission integrations with narrow access
Workflow steps
- Choose the workspace owner Keep the forms and submissions in the workspace that owns the process.
- Assign product roles Use team and workspace roles to separate administration, editing, viewing, and review work.
- Limit external and API access Configure respondent flows and API scopes without giving every actor broad product access.
Concrete examples
Client workspace separation
An agency can keep each client workspace's forms, submissions, members, and branding apart.
Reviewer-only access
A program team can allow review-focused users to inspect submissions without owning team-level settings.
Integration boundary
A sync job can read submissions through an API scope without giving that integration form editing or team administration access.
FAQ
What roles does KinoForms describe publicly?
The public pages describe team owner/admin/member roles and workspace admin/editor/viewer boundaries.
Are respondent access settings the same as workspace roles?
No. Respondent settings govern external form access, while workspace roles govern product access for team members.