Rollout Strategy

Expenses Agent supports two rollout approaches. Select the approach that best fits your deployment before you begin the core configuration steps. Your choice determines whether you complete the pilot-specific configuration tasks during implementation.

Expenses Agent is enabled at the business unit level, allowing you to roll out the feature to one or more business units or validate it with a pilot group before broader deployment.

Important: After you enable Expenses Agent for a business unit, you can’t disable it. Plan phased rollouts carefully before enabling production business units.

Approach	Best for	What to do
Full rollout	Organizations ready to enable Expenses Agent for all users in one or more business units.	Complete the Core Configuration Steps in sequence. No pilot-specific configuration is required.
Pilot rollout	Organizations that want to validate Expenses Agent with a limited group of users before a broader deployment.	Complete the Core Configuration Steps in sequence, incorporating the pilot-specific configuration tasks where indicated.

If you choose a pilot rollout, complete the following pilot-specific tasks at the appropriate points throughout this guide:

Task	Complete in...
Create and categorize the pilot profile option.	Configure a Pilot Rollout
Assign profile values to pilot users.	Configure Profile Values
Configure pilot render conditions for the Expenses navigation tile.	Configure the Expenses Root Menu
Redirect test notifications away from production users.	Configure Testing Notifications