Specialist admin roles

Only available for Premium and Pro accounts.

Specialist admin roles are for people who manage company cards or process travel expenses and need high-level access to specific sensitive information.  

For more information, see Roles and permissions.

Company admin

Only available for Premium and Pro accounts. Multi-role assignment and roles by company are only available on Pro.

The company admin role allows selected users to manage settings, users, and configurations for specific companies within a Perk account.

Company admins only have access to the companies they are assigned to. They can’t view or manage other companies or access account-level settings. This role is designed to let organizations delegate administration to regional or entity-level teams while maintaining overall account control.

Company admins can:

  • Add and manage users, user profiles, and user group settings
  • Set and change roles and permissions for users (except the account admin role)
  • View and manage all trips for their assigned companies
  • Set up and use payment profiles for their companies
  • Manage spend settings such as expense and invoice categories, mileage rates, and business rules
  • Set up cost management settings, including cost objects
  • Manage addresses
  • View spend import logs
  • Edit car preferences and manage corporate codes for their companies
  • Edit company details such as localization settings

Company admins can’t:

  • Set up or configure SSO, user provisioning, or travel and spend integrations
  • Manage the Perk account, including subscriptions and add-ons
  • Create or delete companies, or set a default company for the account
  • Manage travel, spend, or cost management settings for companies outside their scope
  • Review or export spend across all companies
  • Set up or manage travel policies or travel approval processes (these are scoped at the account level)
  • Order or manage corporate cards
  • Assign the account admin role to another user

Note: Travel budget settings are currently not available for company admins. 

Company admin vs. account admin

The key difference is scope.

  • Account admin: Full access to the entire Perk account, including all companies, integrations, billing, and global settings. Can manage account structure and assign admin roles.
  • Company admin: Limited to assigned companies only. Can manage users and configurations within those companies but has no access to account-level settings or cross-company controls.

Note: If you’re on a Premium plan, company admins have access to all companies in the same way as an account admin. However, they can't perform some tasks such as configure SSO, user provisioning or integrations, manage the subscription, and create/delete companies. They can only perform the tasks inherent to the company admin role and can't be assigned another role such as travel manager or financial reviewer. 

Only account admins can assign the account admin role. Learn more about the account admin role in General roles. 

Managing company settings

  • Cost objects: Company admins can view cost objects within their scope, including account-wide ones. They can fully edit only those within their own scope and cannot manage approvers or delegates outside it.

  • Addresses: They can create new addresses and view all account addresses to prevent duplicates. However, they can only edit or delete addresses used exclusively by companies in their scope.

  • Payment profiles: They can assign payment authorisers across the entire account. They can view personal payment profiles for users in their scope but cannot edit personal card settings or access card details.

  • User groups: They can access the User Groups page, but can only create, archive, or manage groups and categories when their scope includes all companies, since these settings are account-wide.

Card admins

This role is only available for Spend customers.

Card admins manage employees’ corporate cards in Perk.

They are responsible for the Perk Card account, checking account information, such as current balance, reservations, and available funds. They can download daily and monthly statements of card transactions performed with all cards for the company.

They can order new cards for employees and approve employees’ card requests, setting card spending limits, restricting spending to specific merchant categories, and allowing ATM withdrawals in the case of physical cards.

Card admins can:

  • Request a card account.
  • Order corporate cards for employees.
  • Set corporate card spending limits.
  • Manage corporate cards, such as freezing or terminating cards.
  • View corporate card transactions.
  • Download card statements.

Card admins can’t:

  • Manage company lodge cards.
  • View spend analytics for cards.
  • Manage transaction settings for expense matching.
  • Manage third-party card transaction integrations.

Travel spend processor

Travel spend processors are responsible for managing expenses associated with trips booked on Perk.

They can check all trip expenses and reassign expenses to other employees, if required. They manage the company’s lodge card, checking that card transactions match trip invoices and changing the lodge card limit, if required.

Travel spend processors can:

  • Manage travel draft expenses.
  • Add a lodge card.
  • Manage company lodge cards.
  • Set lodge card spending limits.
  • View company lodge card transactions.

Travel spend processors can’t:

  • Manage travel bookings on behalf of other people, unlike travel managers.
  • Change travel management settings.
  • Manage travel policies.
  • Skip travel booking approvals.
  • Order or manage corporate cards for employees.

Developer

Only available for Premium and Pro accounts.

Developers are responsible for managing the technical integration of the Perk platform with other third-party systems.

They can set up and configure SSO, user provisioning, and travel and spend integrations. They build their own custom integrations to embed Perk directly into the company’s existing business workflows and improve efficiency by generating API keys to access Perk APIs, subscribing to webhooks, and accessing the Perk sandbox environment.

Developers can:

Developers can’t:

  • Add or delete users or assign roles
  • Review or export spend
  • Manage travel, spend (expense or invoices) or cost management settings
  • View travel or spend reporting
  • Manage company cards
  • Enable spend integrations

Note: The tasks inherent to this role can also be performed by the Account admin.

While developers can set up SCIM and HRIS integrations that create, update or delete users automatically, developers can’t manually manage people in the platform (via People page). However, they can view sync logs to check the integration has been set up correctly.

Was this article helpful?