Permissions are flexible and can be assigned at both the user level and role level, depending on how your organization prefers to manage access.
Overview
Access to your Enaimco environment is defined during onboarding and managed by your organization.
By default:
All users have view access to modules and data (excluding restricted media)
Users cannot create or modify data unless permissions are explicitly granted
Admins can extend access by assigning custom permissions or roles.
Two ways to manage permissions
Enaimco provides two approaches:
1. User Permissions (Individual Access)
Best for quickly assigning permissions to specific users.
Navigate to Admin → Permissions → User Permissions
Search for a user
Select custom permissions from the dropdown
Click Update
This approach is ideal for:
One-off access changes
Temporary permissions
Fine-tuning individual users
2. Role Permissions (Scalable Access)
Best for managing permissions across teams.
Navigate to Admin → Permissions → Role Permissions
Create or edit a role
Assign permissions to the role
Assign users to the role
Roles include:
Name & description
Permission set
Assigned users
This approach is ideal for:
Standardizing access across teams
Scaling user management
Maintaining consistency
Available permissions
The following permissions can be assigned to users or roles:
Permission | Description |
AdminConfiguration | Update app-wide configurations for all users. |
AnomalyCreate | Create new anomalies and edit existing anomalies. |
ActionCreate | Create new actions and edit existing actions. |
AnomalyReview | Review updates to anomalies and decide when to close them. |
AssetEdit | Edit existing asset's properties. |
AssetFileUpload | Upload new files and add them to assets. |
AssetTemplateCreate | Create new asset templates and edit existing asset templates. |
DashboardCreate | Create public dashboards that will be visible to all users. |
DocumentAnalysisCreate | Use AI to extract information from documents. |
DVROperator | Access DVR functionality. |
DVRTester | Access to faked DVR responses for testing purposes. |
BarrierTestCreate | Create new barrier tests in reports. |
EventCreate | Create a timestamp for a video. |
FileEdit | Edit the meta data of a file. |
FileRelationshipEdit | Add/remove relationships between files and other resources. |
InspectionActivityCreate | Create new inspection activities and edit existing inspection activities. |
InspectionActivityReviewer | Review inspection activities. |
InspectionCreate | Create new inspections and edit existing inspections. |
NoteCreate | Add new notes to resources. |
ReadingCreate | Add new readings to assets. |
ReportCreate | Create new public reports that will be visible to all users. |
RiskCreate | Add new risk assessments to assets. |
SensorReadingEdit | Update sensor reading drifts. |
ValveOperationCreate | Create new valve operations. |
ValveMovementRequestCreate | Create and submit valve movement requests. |
ValveMovementRequestReview | Review and approve/reject valve movement requests. |
SchematicEdit | Edit the bounds & tagging in the interactive PID schematic. |
VideoIndexer | Generate Video Index and information about a video. |
ReportGenerateLLM | Create reports using AI. |
DashboardGenerateLLM | Generate dashboards using natural language. |
RovUsageCreate | Create new ROV usage entries. |
RestrictedMediaView | Access to restricted/sensitive media content. |
RestrictedMediaEdit | Manage restricted/sensitive media content. |
Reviewer permissions
Reviewer permissions can also be assigned to support governance workflows.
Reviewers can:
Review changes made by editors
Approve or reject updates before they are finalized
This is especially useful for maintaining data quality and auditability.
How permissions work together
Default state: View-only access
User permissions: Override or supplement access for individuals
Roles: Apply consistent permissions across multiple users
Admins: Control and configure all permissions
💡 Tip: Use roles for structure and user permissions for exceptions
Best practices
Start with view-only access, then expand as needed
Use roles to standardize access across teams
Assign reviewers for critical workflows
Limit admin permissions to a small group
Regularly review access as teams and projects evolve