Skip to main content

Integrations, System, and Access Control

This part of Settings combines platform connectivity with administrative governance. Use it when you need to connect third-party tools, control feature availability, or manage who can do what in your tenant.

Who Can Access This​

RoleAccess Level
AdministratorFull access (admin)
OfficeView and edit (permission-dependent)
SalesView and edit (permission-dependent)
HR AdminView and edit (permission-dependent)
Payroll AdminView and edit (permission-dependent)
TechnicianView only or no access to protected sections

Sections covered here​

  • Integrations: provider setup and system integration controls
  • API Access: Pulse Connect API keys for your branch — see Pulse Connect API Keys
  • Accounting: accounting provider behavior, sync management, and related controls
  • Feature Toggles / Pulse Features: tenant-level capability controls
  • Audit Log: review setting and operational change history
  • User Management: review user accounts and lock or unlock sign-in access
  • Roles & Permissions: role-level permission assignments
  • Impersonation Sessions: review and terminate View As sessions

Integrations and accounting notes​

Integrations are often feature-gated and permission-gated together. For example, provider-specific cards can appear only when matching feature checks pass.

For accounting-specific setup details, use:

That article goes deeper on provider modes, QuickBooks connectivity, and sync queue behavior.

Feature controls and governance​

Feature controls are tenant-level switches. They determine whether a capability exists at all for your company. Role permissions apply after the feature is available.

Use this sequence for safe rollout:

  1. Enable feature for tenant.
  2. Validate with admin account.
  3. Grant role permissions to target users.
  4. Monitor behavior in Audit Log.

User and role administration​

User and role screens control day-to-day authorization boundaries. Keep these principles:

  • Minimize broad admin grants.
  • Use role templates where possible.
  • Review role changes in audit history.
  • Test one non-admin account after permission edits.

Step-by-step guides live in User Management and Roles & Permissions.

View As governance​

Use Impersonation Sessions to monitor active and recent View As activity. Administrators with the View Sessions permission can confirm the original staff member and viewed account, review the recorded reason, and terminate an active session. See View As and Impersonation Sessions for the eligibility rules and safe operating steps.

Troubleshooting​

Integration card is missing​

The required feature key may be disabled for your tenant.

User can open a section but cannot perform action buttons​

They likely have read-level coverage without update/admin permission for that area.

Feature enabled but still hidden for users​

Check role-level permission dependencies after enabling tenant-level feature access.