Anyone who has worked with a marketing automation platform knows one thing: permissions matter.
Too many rights, and you expose your database and workflows to risk.
Too few, and you slow down execution.
The goal is simple: allow everyone to work freely — but within their role.
Let’s see how Paminga handles permissions in a smart and highly granular way.
The Paminga structure: Users, Teams and Roles
Inside Account Settings, permissions are structured around:
- Users
- Teams
- Roles
Permissions are grouped into roles. These roles can be assigned:
- Directly to a user
- Or to a team (rights are cumulative)
You can create as many roles as needed: junior, agency, regional admin, global admin, etc.
Five major permission families
1. Administrative
Global configuration permissions.
2. Assets
Create, update, delete and publish emails, forms, landing pages, CTAs and brand kits.
3. Workflows & Automations
Create and edit workflows — and control who can execute them.
4. Data Management
Manage accounts, contacts, custom objects, imports and exports.
5. Finder (Workspaces & Folders)
Control visibility and sharing across workspaces and folders.
Granular control down to field level
One of the strongest features in Paminga is field-level permissions.
You can decide:
- Who can update field values
- Field by field
- Across accounts, contacts, standard and custom fields
A junior profile can view data without being able to modify it.
This protects your integrated CRM layer while keeping transparency.
Example: the “Junior” role
Imagine onboarding a junior marketer.
You can configure a dedicated role that:
- Allows workflow creation and updates
- Prevents workflow execution
- Allows applying brand kits
- Prevents creating or deleting brand kits
- Allows data visibility
- Prevents deletion of objects or contacts
The result: the junior can work, learn and build — without breaking anything.
Workspace-based visibility: perfect for multi-region organizations
Through the Finder permissions, you can:
- Create regional workspaces (EMEA, Americas, APAC)
- Share specific folders with specific teams
- Maintain a central workspace
- Give a dedicated folder to an external agency
Visibility can be defined:
- At global level
- At regional level
- At country level
- At folder level
This makes Paminga suitable for both mid-sized companies and large enterprise environments.
Why this matters strategically
Proper permission management:
- Secures your data
- Prevents human errors
- Accelerates onboarding
- Enables safe collaboration with agencies
- Improves marketing governance
Paminga strikes the right balance between execution freedom and structural control.
Conclusion
Whether you are a growing company or a global enterprise, you can define permissions precisely at:
- Global level
- Regional level
- Team level
- User level
Everyone works within their scope — nothing more, nothing less.
In a modern marketing ecosystem, that level of precision is not optional. It is foundational.
