Workspaces and folders
Organize Mokaform forms and questionnaires with organizations, workspaces, folders, project naming, and move workflows.
Mokaform uses a simple hierarchy: organization, workspace, folder, questionnaire.
PRO feature
Creating additional workspaces and folders is a PRO feature. Use the default workspace to start, then upgrade when you need separate team, client, or project areas.
How the hierarchy works
| Level | Purpose |
|---|---|
| Organization | Holds global settings, domains, billing, and organization members. |
| Workspace | Separates teams, clients, departments, or projects. Workspace members can have their own roles. |
| Folder | Groups related questionnaires inside a workspace. |
| Questionnaire | The form itself, including builder, summary, submissions, share, connections, and settings. |
Use workspaces when access should differ. Use folders when the same team needs a cleaner list.
Recommended workflow
Create or choose the organization.
Create a workspace for the team, client, department, or project.
Invite workspace members with the role they need.
Create folders for active form groups.
Create questionnaires inside the right folder.
Workspace examples
| Workspace | Folder examples |
|---|---|
| Marketing | Lead capture, events, campaign feedback, newsletter |
| Customer success | NPS, onboarding, cancellation, support follow-up |
| People ops | Hiring, onboarding, employee feedback, requests |
| Agency client | Intake, approvals, feedback, reports |
| Product | Research, beta testing, feature requests, usability |
Folder practices
- Keep folders broad enough that people can find things quickly.
- Use dates only when they matter, such as
Events 2026orQ3 research. - Archive or rename old folders instead of letting active work get buried.
- Keep template forms in a dedicated folder if your team copies them often.
- Put private or sensitive forms in a workspace with restricted membership, not just a separate folder.
Moving forms
Move a questionnaire when the ownership or working context changes. Before moving it, check:
- Who needs access in the destination workspace.
- Whether connected integrations still point to the right destination.
- Whether exported response processes or internal bookmarks rely on the old location.
- Whether the form should keep the same public link.