integration_instructions Integrations
expand_more
admin_panel_settings

Security & Permissions

ACL Matrix

Structured permission model defining access and management based on role and scope. Keep your business information safe and organized with smart permissions that ensure everyone sees exactly what they need to see — nothing more, nothing less.

  • verified_user6 Role Types
  • account_treeOrg, Dept & Project Scopes
  • person_addDirect Admin Assignments
ACL Matrix Access Control Overview

Control access based on user roles

Define clear boundaries and scopes.

Different responsibilities map to different actions — isolated by role, department, and project. Six role types cover every kind of user in the system.

01 domain

Org Admin

Full control over the entire organization, departments, and system configurations.

02 business

Dept Admin

Manage projects and members within their assigned department scope.

03 folder_shared

Project Admin

Admin permissions isolated to the specific project they are assigned to.

04 person

Normal User

Access assigned cards and collaborate with team members on tasks.

05 assignment

Submitter User

Log in to view, access, and submit assigned internal forms.

06 public

Public User

Access and submit forms publicly via shared links without account logins.

Interactive simulator

See what each role can do in real time.

Click on any role to see their scope, permissions, and available resource access.

admin_panel_settings
Org Admin Entire Organization
business
Dept Admin Assigned Department
folder_shared
Project Admin Assigned Project
person
Normal User Assigned Cards / Work
assignment
Submitter User Assigned Forms Only
public
Public User Shared Form Links

Org Admin permissions

The Org Admin has organization-level access across Mynix, with complete control over all data assets, departments, users, and billing settings.

Resource Scope
Read / View
Create / Add
Modify / Edit
Delete Access
Organization / System
check_circle
check_circle
check_circle
check_circle
Departments / Teams
check_circle
check_circle
check_circle
check_circle
Projects / Boards
check_circle
check_circle
check_circle
check_circle
Workflows / Card Items
check_circle
check_circle
check_circle
check_circle
Forms / Submissions
check_circle
check_circle
check_circle
check_circle

Understand user access

Each role has a defined scope.

Users only receive access appropriate to their responsibilities. Here is the full matrix.

User Type Access Scope Key Permissions
Org Admin Entire Organization Add Edit Delete across all departments and workflows
Dept Admin Assigned Department and its Projects Add Edit Delete restricted to the assigned department scope
Project Admin Assigned Project Add Edit Delete of boards, cards, and team roles within that project
Normal User Assigned Cards / Projects Add cards, view project items, edit and shift status on assigned cards
Submitter User Assigned Forms Log in, view form fields, and submit records to the database
Public User Shared Public Forms Access public links and submit forms without an active Mynix account

Why use ACL Matrix

Without structure, permissions become complex.

Mynix simplifies this with role-based access and clear scope boundaries.

security

Clear Role-based Access

Users receive access automatically based on their assigned role and responsibilities.

admin_panel_settings

Controlled Admin Access

Department and project administration can be assigned specifically where required.

remove_moderator

Reduced Unnecessary Access

Users don't need organization-wide permissions when their scope is a single card or form.

people

Support Different User Types

Separate permissions for internal admins, regular users, submitters, or external guest forms.

Detailed role breakdown

How permissions operate for each user class.

And where to assign admin scopes across the platform.

admin_panel_settings
1. Org Admin

Has full organization-level access across Mynix, with permissions to Add, Edit, and Delete across all departments, user bases, workflows, custom fields, and billing items.

business
2. Dept Admin

Can access and manage resources under their assigned department. Permissions include department settings, workflow creations, and department-level user mappings.

folder_shared
3. Project Admin

Administrative access inside a specific project. They can invite team members, assign cards, change workflows, and update settings for that board only.

person
4. Normal User

Standard company team members. They can append cards, view workflows, edit values on cards assigned to them, and collaborate on tasks.

assignment
5. Submitter User

Intended for users who only input values. They can log in but their sole capability is access and submission of internal forms assigned to them.

public
6. Public User

Allows external partners, customers, or participants to submit data without an active Mynix account through a shared public form link.

Three levels of business privacy

Control information transparency.

Public, restricted, or completely private — choose the level that matches the data.

public

Public Info

Accessible by everyone in your organization. Perfect for company manuals, standard guidelines, shared repositories, and events.

group

Private to Team

Restricted to members of specific departments or projects. Used for day-to-day workflow tasks, client lists, and operational data.

lock

Confidential

Only visible to specific authorized individuals. Essential for files like payroll spreadsheets, client contracts, and CFO reports.

No separate configuration required

Admin roles are managed where the work lives.

Adding a department or project admin is seamlessly embedded in standard administration tabs.

  • business
    Dept Admin Settings

    Department → Settings → Admin → Search User → Add User

  • folder_shared
    Project Admin Settings

    Project → Project Team → User List → Make User Project Admin

info_outline
No separate ACL setup required

Mynix maps permissions instantly based on these assignments.

Access Control Setup Progression

Real-world scenarios

How different industries structure roles.

See how teams protect critical assets with role-based access.

campaign

Marketing Agency

Isolate client workspaces. Designers see only their assigned projects, while client accounts run on Guest/Public forms.

local_hospital

Healthcare Practice

Strict patient charts isolation. Doctors have full access, receptionists view appointments, and billing team gets specific form access.

code

Software Developer

Release flows. Project Admins handle sprints, developers push code cards, and outside QA analysts submit issue tickets.

account_balance

Financial Firm

Strict audit boundaries. Advisors access local portfolios, Compliance officers get read-only verification access across all sheets.

Top-down hierarchy

Every user gets the right level of access.

Administrators retain full visibility, team members focus on executing work, and external stakeholders write data through form validation.

Org AdminOrganization-level access
arrow_downward
Dept AdminDepartment-level access
arrow_downward
Project AdminProject-level access
arrow_downward
Normal UserAssigned card items
arrow_downward
Submitter UserAssigned form inputs
arrow_downward
Public UserPublic form link submissions

Secure every user with the right level of access.

Define roles, assign scopes, and enforce data isolation across your organization with the ACL Matrix.