Access Level Control in GTG CRM: Keeping Data Secure, Clearly Defined Permissions

What is Permissions?

Permissions in GTG CRM help businesses clearly define: - What each user can view - Which data they can edit - What actions they are allowed to perform within the system

By setting up roles with specific permissions, businesses ensure that each person only handles their assigned tasks.

Why Do Businesses Need Permissions?

Risks of NOT Having Permissions

Problem	Consequences
Data accessed freely	Customer information, revenue is leaked
Overlapping tasks	Multiple people working on the same task
Uncontrolled errors	Accidentally deleting or editing important data
Sensitive information leaked	Employees see salaries, expenses, strategies

Benefits of Having Permissions

Benefit	Description
Secure Operations	Each person only sees/does their assigned part
Prevent Errors	No one accidentally deletes/edits critical data
Easy Scalability	Adding new employees just requires role assignment
Easy Management	Clearly know who does what, responsibilities are clear

Default Roles

GTG CRM offers 3 default roles:

Administrator

• The highest level of permissions in the system
• Can perform all actions on the platform
• Automatically has access to Settings

Marketing Manager

• Manages marketing campaigns
• Views reports and statistics
• Manages the marketing team

Marketing Staff

• Performs daily marketing tasks
• Has more limited permissions than a Manager

Custom Permissions by Module

Customize permissions for each module with toggle on/off:

Module	Permissions That Can Be Granted
Automation Workflow	Create, View, Update, Delete
Landing Page	Create, Update, Publish, Unpublish, Delete, Modify Custom Domain
Marketing	View Social Posts, Manage Campaigns
CRM	View All Contacts, Import, Export, Edit, Delete
Email	Create, Send, View Reports
Messaging	View, Reply, Manage Channels
Product Hub	Manage Products, View Inventory
E-commerce	Manage Orders, View Reports
Billing	View Invoice, Manage Payment
Settings	Manage Workspace, Manage Users

Standardized Permission Naming: DOMAIN_ACTION_OBJECT

Naming Convention

All permission names in GTG CRM are standardized according to Convention A - DOMAIN_ACTION_OBJECT:

DOMAIN_ACTION_OBJECT
  │         │       │
  │         │       └── Object (entity being acted upon: INVOICE, USER, CONTACT...)
  │         └── Action (verb: VIEW, CREATE, MANAGE, DELETE...)
  └── Domain (area: BILLING, WORKSPACE, CRM, AUTOMATION...)

Examples of Convention A Permission Names

Domain	Permission Name	Meaning
BILLING_	BILLING_VIEW_INVOICE	View invoice
BILLING_	BILLING_ADD_PAYMENT_METHOD	Add payment method
WORKSPACE_	WORKSPACE_ACTION_USER	Manage workspace users
WORKSPACE_	WORKSPACE_VIEW_BILLING_MEMBER	View billing information
AUTOMATION_	AUTOMATION_WORKFLOW_CREATE	Create automation workflow
AUTOMATION_	AUTOMATION_WORKFLOW_DELETE	Delete automation workflow
CRM_	CRM_OBJECT_VIEW	View CRM object
CRM_	CRM_VIEW_ALL_CONTACT	View all contacts

Why is Convention A Necessary?

Previously, permission names were inconsistent: SEND_EMAIL, CREATE_LANDING_PAGE, VIEW_BILLING — making them difficult to understand and manage when a business has dozens of different permissions.

Convention A solves this problem by: - Clearly grouping by Domain → easy to find related permissions - Consistent actions → VIEW always means view, CREATE always means create - Easy to audit → just search for BILLING_ to see all billing-related permissions

Administrator Automatically Accesses Settings

Users with the Administrator role automatically have access to all Settings — no additional permissions need to be assigned.

Permission Workflow

┌─────────────┐    ┌─────────────┐    ┌─────────────┐
│  Create New │ ─► │  Customize  │ ─► │  Assign Role│
│  Role       │    │  Permissions│    │  to User    │
└─────────────┘    └─────────────┘    └─────────────┘
      │                  │                  │
      ▼                  ▼                  ▼
   Name,            Toggle each           Select user,
   description      permission            select role

Example: Assigning Permissions to Departments

Role	Primary Domain	Example Convention A Permissions
CEO/Owner	All	Administrator
Sales	CRM, Messaging, Email	CRM_VIEW_ALL_CONTACT, CRM_OBJECT_VIEW
Marketing	Marketing, Ads, Landing Page	AUTOMATION_WORKFLOW_CREATE, LANDING_PAGE_CREATE
Support	Messaging, Ticket	CRM_OBJECT_VIEW (read-only)
Warehouse	Product, Order	(module-specific)
Finance	Billing	BILLING_VIEW_INVOICE, BILLING_ADD_PAYMENT_METHOD

Summary

With Permissions in GTG CRM:

• Scale your team while maintaining control
• Protect your business's sensitive data
• Standardized Convention A permission names - clear and easy to audit
• Administrators automatically get Settings access - no more misconfigurations
• Operate professionally like a large enterprise