Permissions & Roles for Goals

Modified on Mon, 17 Nov at 10:23 PM

Permissions & Roles for Goals

Overview

Goal Management in ARMOR is controlled by user roles and permissions. Understanding who can create, edit, view, and manage goals ensures your organization maintains proper oversight while empowering the right people to monitor performance.

This article explains the permission structure for Goals and how different user roles interact with goal monitoring features.

User Roles and Goal Permissions

Super Admin

Full Goal Management Access

Super Admins have unrestricted access to all goal features across all accounts in the system:

  • ✅ Create goals for any account
  • ✅ Edit any goal in the system
  • ✅ Delete any goal
  • ✅ View all goal alerts across all accounts
  • ✅ Configure goal scoping (account, site, asset, tag-based)
  • ✅ Access goal analytics and reporting

Typical Use Cases:

  • ARMOR system administrators
  • Setting up goals during customer onboarding
  • Troubleshooting goal configuration issues

Account Admin

Full Goal Management Within Their Account

Account Admins have complete control over goals within their assigned account(s):

  • ✅ Create goals for their account
  • ✅ Edit goals they created or that were created for their account
  • ✅ Delete goals within their account
  • ✅ View all goal alerts for their account's assets
  • ✅ Configure goal scoping (site, asset, tag-based within their account)
  • ✅ Access goal performance reports for their fleet

Typical Use Cases:

  • Fleet managers setting operational targets
  • Operations directors monitoring utilization standards
  • Maintenance managers tracking service intervals
? Account Scope Automatic Restriction

When an Account Admin creates a goal, it's automatically scoped to their account. They cannot create goals for other accounts or see goals from other customers.

Site Manager

Limited Goal Visibility

Site Managers can view goals but cannot create or modify them:

  • ❌ Cannot create goals
  • ❌ Cannot edit or delete goals
  • ✅ Can view goal alerts for assets at their assigned sites
  • ✅ Can see goal status on asset detail pages
  • ✅ Can acknowledge or dismiss goal-related alerts (if they have alert permissions)

Typical Use Cases:

  • Site supervisors monitoring location-specific performance
  • Warehouse managers tracking equipment utilization
  • Operations coordinators reviewing daily goal status

Basic User

View-Only Goal Access

Basic Users have read-only access to goal information:

  • ❌ Cannot create, edit, or delete goals
  • ✅ Can view goal status on assets they have access to
  • ✅ Can see goal alerts in their alerts feed (for assets they manage)
  • ❌ Cannot access the Goal Management admin page

Typical Use Cases:

  • Technicians viewing asset performance metrics
  • Operators checking if their equipment meets targets
  • Drivers seeing daily runtime or distance goals

Permission Summary Table

Action Super Admin Account Admin Site Manager Basic User
Create Goals
Edit Goals ✅*
Delete Goals ✅*
View Goal Management Page
View Goal Alerts ✅** ✅**
Export Goal Data

* Account Admins can only edit/delete goals within their own account
** Only for assets they have permission to view

Accessing Goal Management

For Super Admins and Account Admins

  1. Log into the ARMOR web portal
  2. Navigate to Administration in the main menu
  3. Select Goal Management

From here, you can create, view, edit, and delete goals as permitted by your role.

For Site Managers and Basic Users

Goal alerts appear automatically in:

  • The Alerts page (if enabled for your role)
  • Asset detail pages - Shows goal status and current values
  • Email notifications (if configured)

Goal Scoping and Permissions

Account-Level Scoping

Goals are always scoped to a specific account. Users can only create goals for accounts they have access to:

  • Super Admins - Can select any account in the system
  • Account Admins - Automatically restricted to their own account(s)

Site and Asset Scoping

When creating a goal, admins can further restrict scope to:

  • Specific Sites - Goal applies only to assets at selected sites
  • Specific Assets - Goal applies only to individually selected assets
  • Tag-Based Filtering - Goal applies to assets matching specific tags (e.g., "forklift" or "warehouse-a")
⚠️ Important: Users can only scope goals to sites and assets they have permission to view. The system automatically filters the available options based on your access level.

Alert Visibility

Goal alerts follow the same permission structure as other ARMOR alerts:

  • Users only see alerts for assets they have permission to view
  • Alert visibility respects site-level and asset-level permissions
  • Email notifications are sent based on user notification preferences

Common Permission Scenarios

Scenario 1: Fleet Manager Setting Up Goals

Role: Account Admin

What they can do:

  • Create goals for their entire fleet
  • Set different goals for different sites (e.g., stricter runtime targets for main warehouse)
  • Configure tag-based goals to apply to specific equipment types
  • View all goal alerts across their account

Scenario 2: Warehouse Supervisor Monitoring Performance

Role: Site Manager

What they can do:

  • View goal alerts for assets at their warehouse
  • Check goal status on individual forklifts
  • See which equipment is meeting or missing targets
  • Cannot modify goal thresholds (must request changes from Account Admin)

Scenario 3: Equipment Operator Checking Daily Goals

Role: Basic User

What they can do:

  • View goal status on their assigned asset(s)
  • See current performance vs. target on asset detail page
  • Receive alerts if their asset triggers a goal
  • Cannot see the Goal Management admin interface

Requesting Access Changes

If you need different goal permissions:

  1. Contact your organization's Account Admin or Super Admin
  2. Explain what goal management capabilities you need
  3. They can adjust your user role or grant additional permissions
? Tip: Most organizations limit goal creation to Account Admins to maintain consistent monitoring standards. This prevents conflicting goals and ensures fleet-wide alignment.

Best Practices

For Account Admins

  • Document your goal strategy so all admins follow the same approach
  • Create goals with clear, descriptive names so all users understand what's being monitored
  • Use consistent threshold values across similar equipment types
  • Review goal alerts regularly to ensure they're actionable and not creating alert fatigue

For Organizations

  • Designate 1-2 people as primary goal administrators to maintain consistency
  • Train Site Managers on how to interpret goal alerts (even though they can't edit goals)
  • Ensure Basic Users understand what goals mean and how they're measured
  • Regularly audit active goals to remove outdated or unused monitoring rules

Common Questions

Can a Site Manager request a new goal?

Yes, but they'll need to coordinate with an Account Admin who has the permissions to create it. Site Managers should provide the Account Admin with details about what they want to monitor and why.

Why can't I see the Goal Management page?

The Goal Management page is only visible to Super Admins and Account Admins. If you need access, contact your Account Admin to request a role change.

Can I see goals from other accounts?

No (unless you're a Super Admin). Account Admins and below can only see goals within their own account. This ensures customer data isolation and privacy.

Who receives goal alert notifications?

Alert notifications are sent based on each user's notification preferences and their access to the affected assets. All users with access to an asset will see goal alerts for that asset (based on their role permissions).

Next Steps

Getting Help

If you have questions about goal permissions or need help with role configuration, contact the ARMOR Support Team.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article