Chrona, A Konfigure8 productDOCSWebsite
Account and billingGlossarySupport

Install Chrona Workforce Scheduler

Chrona Workforce Scheduler adds rostering to Chrona Scheduler: roles built from skills, availability and leave, hours against capacity, agreements with rest, hours, overtime and night shift rules, demand and the coverage strip, shift types and coverage with generation, roster periods with publish, a roster import from Excel, Mark absent with a repair that moves only open shifts and on-call shifts, wages and overtime hours, and the Outcomes of each roster. It installs as a second solution on top of Chrona Scheduler and brings its own app. Same board. Chrona Workforce Mobile, the app your workers use on their phones, is a third solution in the same download: import it only if you want the mobile app.

View as Markdown
Page tools
View as Markdown
On this pageWhat you need1. Import the first two solutions, in order2. Give users access3. Open the app4. Optional: turn on auditing before you add agreements5. Connect and run Auto Schedule6. Set up Chrona Workforce Mobile7. Turn on scheduled tasksUpdate to a newer versionHelp

Set up with an AI agent: connect the Chrona MCP server at https://mcp.chrona365.com/mcp (Streamable HTTP, authentication None) for setup guidance, agreement recipes and roster-import mapping. Set up your agent, or follow the manual steps below. Chrona MCP cannot access your environment; changes need your agent’s separately authenticated Dataverse tools. Solution import and publishing need the Dataverse CLI, another authenticated Web API client or your actions in the maker portal.

What you need

  • A Power Platform environment with Dataverse, where you are a System Administrator or System Customizer.
  • A Chrona account for your organization in the Chrona Portal at https://portal.chrona365.com. Chrona Workforce Scheduler is free for the first five workers Auto Schedule schedules each month; for more, start the 14-day trial or subscribe under Plan and billing.
  • ChronaWorkforceScheduler-<version>.zip, from Downloads in the Chrona Portal. Unzip it: it holds this guide and three solutions, with the release in their names, for example 01-ChronaScheduler_0_1_24_managed.zip.
    • 01-ChronaScheduler_<version>_managed.zip: Chrona Scheduler, with the control, its settings tables and the connection to Chrona.
    • 02-ChronaWorkforceScheduler_<version>_managed.zip: the Workforce tables and the Chrona Workforce Scheduler app.
    • 03-ChronaMobile_<version>_managed.zip: Chrona Workforce Mobile, with the worker website and the worker directory flows. Optional: import it only for the mobile app (step 6).

1. Import the first two solutions, in order

  1. Open https://make.powerapps.com and pick your environment at the top right.
  2. Select Solutions, then Import solution.
  3. Select Browse, choose 01-ChronaScheduler_<version>_managed.zip, then select Next. If the wizard shows two addresses already filled in, leave them as they are. Leave Enable plug-in steps and flows included in the solution ticked under Advanced settings; it is ticked by default. Select Import. If Chrona Scheduler is already installed, this updates it to the version that matches Workforce.
  4. When that import has finished, import 02-ChronaWorkforceScheduler_<version>_managed.zip the same way. The wizard asks for one connection. For Chrona Scheduled tasks Dataverse, choose or create your own Microsoft Dataverse connection: the two scheduled tasks flows of step 7 then run as you. If Next stays unavailable after you create a connection, select the back arrow at the top of the panel, then Next again. If the import stops with a message that another import is running, or reports a failure after about 35 minutes, wait a few minutes. Then check whether it worked. On the Solutions page, select Chrona Workforce Scheduler, then select See history on the command bar. If the latest import of ChronaWorkforceScheduler shows the Result Success and the solutions list shows the new version, the install worked.
  5. Both solutions appear in the list. The banner may say that labels for a language could not be imported: Dataverse installs labels only for languages enabled in the environment, and the import still succeeds.

For the mobile app, import the third file as in step 6.

All solutions are managed. To update, see Update to a newer version. To remove them, delete Chrona Workforce Mobile first if you installed it, then Chrona Workforce Scheduler, then Chrona Scheduler.

2. Give users access

  • Planners need the security role Chrona Workforce User. It lets them open the Chrona Workforce Scheduler app, add workers and edit their skills.
  • A Chrona Workforce Admin then adds them to each scheduler in its Access settings (the board’s gear, Access). Users who change a scheduler’s shift types, coverage and rules go on its Change settings list.
  • Users who set up agreements, skills, roles, sites and schedulers need Chrona Workforce Admin.
  • System Administrators need nothing more.

Assign roles in the Power Platform admin center: Environments, your environment, Settings, Users + permissions, Users, select the user, Manage security roles. With version 0.1.33 or earlier, also give each user Basic User: without it, Power Apps refuses the app with the error “missing prvReadAppModule privilege”.

3. Open the app

In https://make.powerapps.com, select Apps and play Chrona Workforce Scheduler. Its pages hold your roster data:

  • Schedulers: your schedulers, with the shifts that need cover and the requests that wait for you. Select a scheduler to open its board, where you import from Excel, plan, generate, run Auto Schedule and repair. Its Requests tab holds the requests of its workers. The gear on the board opens the scheduler’s settings under the board. With more than one scheduler, select the scheduler’s name on the board to switch to another; the board keeps the same day and the same Day, Week or Month. Workers on the board (on the toolbar, or under Actions) lists who works there: add workers before you run Auto Schedule.
  • Workers: the workers you roster, with their roles and skills. App status shows who uses Chrona Workforce Mobile; Invite to app invites the selected worker.
  • Agreements: the rules of your award or agreement, the workers under each one, and the agreement document.
  • Skills and Roles: what each role needs.
  • Availability types: the kinds of leave and other time off. Availability: patterns for when workers can work, and each employment type’s default pattern and phone switch.
  • Shift types and Coverage: your shifts and their times, and how many workers each role needs on them, for Generate on the board.
  • Demand and Demand drivers: how many workers you need, and when.
  • Integration Studio: file formats, confirmed code maps and export actions. See Export hours and staffing reports for setup, checks, corrections and delivery. Automatic actions use the scheduled tasks flow in step 7.
  • Sites and Holiday calendars: where workers work, and each site’s public holidays. On a site, set Region first, then Holiday calendar and Time zone: both lists show only the region’s. A new holiday calendar with a region gets that region’s public holidays for this year and next year; Fetch latest gets the newest. A shift on a public holiday counts in the Sundays and public holidays worked rule.

Mobile, at the bottom of the left pane, holds App access and Setup of Chrona Workforce Mobile; see step 6. Users with the role Chrona Workforce Admin, or a System Administrator, see them. Until you import the third file, both pages and Invite to app say that Chrona Workforce Mobile is not installed.

4. Optional: turn on auditing before you add agreements

Chrona Workforce Scheduler ships with auditing off, and turning it on is your choice. Without auditing, Modified By and Modified On keep only the last change. With auditing on, each change to an agreement, a rule or a worker’s agreement keeps who made it, when, and the old and new values. History starts on the day you turn it on, so if you want it, do it before you enter the first rule.

  1. In the Power Platform admin center, select Manage, Environments and your environment. Select Settings, expand Audit and logs, and select Audit settings. Select Start Auditing, then Save.
  2. In https://make.powerapps.com, select Tables, then All, and open Agreement. Select Properties, expand Advanced options, select Audit changes to its data, then Save. Do the same for Agreement rule and Worker.
  3. In Worker, select Columns, then All columns, and open Agreement. Expand Advanced options, select Enable auditing, then Save.

Auditing the Worker table also records changes to its other audited columns, such as Hours per week.

5. Connect and run Auto Schedule

On the board, select Auto Schedule. If your environment is not connected to Chrona yet, the first run connects it, in the same one step as Chrona Scheduler. Your plan belongs to your organization, so every environment it connects is covered.

A calendar created from this app uses Chrona Workforce Scheduler and always has a site. Add a site under Sites first. When the first run connects a board that has no scheduler yet, the board makes one at your only site; with several sites it asks which one; with none it asks you to add a site first. For a calendar created elsewhere, give it its Site, then set its Product to Chrona Workforce Scheduler in its settings.

Plan and billing in the Chrona Portal shows your usage and charges. Pricing: https://chrona365.com/workforce/pricing.

6. Set up Chrona Workforce Mobile

Chrona Workforce Mobile is the app your workers use on their phones: their shifts, leave requests and time. It runs on a Power Pages website in your environment. Skip this step if you do not want the mobile app.

  1. Allow script files. The website’s app files include .js files, which Dataverse blocks by default. In the Power Platform admin center, select Manage, Environments and your environment, then Settings, Product, Privacy + Security. Remove js from Blocked attachments, then Save.
  2. Import 03-ChronaMobile_<version>_managed.zip as in step 1, after Chrona Workforce Scheduler. The wizard asks for three connections, used by the worker directory flows: choose or create a Microsoft Dataverse connection, an Office 365 Groups connection and an Office 365 Users connection. Each is made with a sign-in, with nothing to type. The Office 365 Users connection needs an account with a mailbox. Office 365 Groups does not read role-assignable groups. If Next stays unavailable after you create a connection, select the back arrow at the top of the panel, then Next again. The wizard then shows the two worker directory settings; leave them as they are: Chrona sets both when you connect the website in item 5, unless a value is already set. The worker directory flows stay off until you set up the worker directory: https://chrona365.com/docs/workforce-mobile-directory. This import takes longer, as it brings the website.
  3. Open https://make.powerpages.microsoft.com, pick your environment, select Inactive sites and Reactivate Chrona Workforce Mobile. Power Pages takes a few minutes to set the site up.
  4. Make the website public, so workers can reach it from their phones. In Power Pages, edit the site, select Security, then Site visibility, and select Public. A new site is private: only you and the users you share it with can open it. A Power Platform administrator or a Dynamics 365 administrator can do this. A System administrator can too, unless your organization’s settings stop it. If the choice is unavailable, ask your administrator to allow public access for non-production sites. A site in a developer environment always stays private. The site restarts, so allow a few minutes.
  5. In the Chrona Workforce Scheduler app, switch to Mobile and select Setup. Until a website is connected, it opens on Connect your worker website: choose the website, then check its app user (Setup selects the newest app user named # Portals- followed by the website’s name), enter your organization’s name and time zone, and select Connect website. Chrona then sets the two worker directory settings, unless a value is already set. If it cannot set one, the page names it, says why and says how to set it yourself.
  6. Check what workers can do in the app. A connected website lets workers make requests and record their time. To change this, on Setup select App settings, then Features: Let workers make requests and record time. Who may change their availability from the phone is set per employment type, on the Availability page.
  7. Give the users who manage workers the role Chrona Workforce Admin, as in step 2.
  8. Invite workers from App access, with Invite to app on Workers, or from the board. Each worker gets an email from the sender’s mailbox; the sender’s mailbox must be approved in your environment. Workers who sign in with a work account of your organization need that account as their User before you invite them: add them from Users on the board’s Workers, or pick their User on their record in Workers. The invitation then links their work account to the app. When workers first sign in, Microsoft may ask them to accept the website’s sign-in permissions; an administrator can accept once for your whole organization.

The website keeps its address when you update Chrona Workforce Mobile. If you remove Chrona Workforce Mobile and import it again, the website has no address until you reactivate it as in item 3, and Setup says so. If Inactive sites does not list it, delete the site in the Power Platform admin center (Manage > Power Pages > the site > Manage > Site Actions > Delete this site), then reactivate it as in item 3. The delete removes the site’s hosting and keeps its pages and settings in your environment. Inactive sites lists the site again. Reactivating it gives it a new address and a new app user.

7. Turn on scheduled tasks

Two cloud flows run Chrona’s work in the background. Chrona Scheduled tasks runs each hour: the staffing check keeps open shifts in line with the counts, call-outs start for open shifts that enter their horizon, and old demand driver values are cleaned up. Chrona Call-out timer opens each next level of a call-out at its time. Both flows use the connection reference Chrona Scheduled tasks Dataverse.

If you picked the connection for Chrona Scheduled tasks Dataverse in the import wizard (step 1), both flows are on after the import. They run as you, on your own connection. Both flows are associated with the Chrona Workforce Scheduler app, and the app has in-app notifications on, so Workforce admins hear when a task keeps failing. Each admin who must get the notice also needs a role that lets them receive app notifications, such as Basic User.

Check that the tasks run: in the app, Configuration > Auto Task Log shows each task’s last and next run. When a task is more than 2 hours past its next run, the page says that tasks are overdue.

From the command line or a pipeline: give the import your connection in a deployment settings file, Microsoft’s way to set a connection at import.

  1. Find your connection’s Id: pac connection list --environment <your environment URL>. Use one on /providers/Microsoft.PowerApps/apis/shared_commondataserviceforapps whose Status is Connected. It must be your own connection, or shared with you.
  2. Write the file: pac solution create-settings --solution-zip 02-ChronaWorkforceScheduler_<version>_managed.zip --settings-file chrona-settings.json. In it, set ConnectionId of chr_scheduledtasks_dataverse to that Id.
  3. Import with it: pac solution import --environment <your environment URL> --path 02-ChronaWorkforceScheduler_<version>_managed.zip --settings-file chrona-settings.json --activate-plugins --publish-changes. For Chrona Workforce Mobile, do the same with 03-ChronaMobile_<version>_managed.zip: take the Ids of its Dataverse, Office 365 Groups and Office 365 Users connections from the same pac connection list, and set EnvironmentVariables to [] in its file (the worker directory settings are set as in step 6, item 5).

If the import fails with “An unexpected error occurred”, check the Id against pac connection list: A connection that does not exist gives that message.

If the flows are off: after an import without a connection, such as one from the command line or a pipeline without a settings file, check Auto Task Log an hour later. If it says that tasks are overdue, or a flow is off, do these steps as the admin who imported the solutions, with the role System Administrator or Chrona Workforce Admin. The flows then run as you, on your own connection:

  1. Make your connection. In https://make.powerapps.com, pick your environment, select Connections > New connection and search for “Dataverse”. Two connectors are named Microsoft Dataverse. Select + on the one with the green, round icon and the text “Provides access to Microsoft Dataverse actions and triggers for Power Platform environments”. Do not use Microsoft Dataverse (legacy), with the grey, square icon: its connection cannot be used on the connection reference. Keep OAuth, select Create and sign in as yourself. If you already have a connection on the green connector, you can use it.
  2. Bind it. In Power Apps, open Solutions > Default Solution > Connection references > Chrona Scheduled tasks Dataverse > Edit. Pick your connection, then select Save > Save changes. Use Default Solution: Edit is disabled on this connection reference inside Chrona Workforce Scheduler, a managed solution.
  3. In Power Automate (https://make.powerautomate.com), pick your environment and open Solutions > Chrona Workforce Scheduler > Cloud flows. Open Chrona Scheduled tasks and select Turn on. Do the same for Chrona Call-out timer. Chrona Scheduled tasks runs once straight away: after about a minute, its run history shows Succeeded.

Licence: Microsoft licenses an automated or scheduled flow by its owner, whatever connection it uses. For a flow associated with an app, “the owner needs Power Apps Premium license, or a Dynamics 365 license” (Power Automate licensing FAQ). So if you own the flows, the Power Apps Premium or Dynamics 365 licence you use for the app covers them.

If you leave: the flows depend on your account, so they stop when it is disabled or removed. The Auto Task Log then says that tasks are overdue, and planners see on the board that the staffing check has not run. Another admin makes themselves the owner of both flows (on the flow, Details > Edit), makes their own connection and binds it as in items 1 and 2 above, and turns the flows on again as in item 3. Or they use the route below.

If you prefer the flows not to depend on a person: run them as an application user, with these steps instead of items 1 and 2 above. Microsoft licenses a flow that a service principal owns with a Power Automate Process licence for each flow, or with a licensed user designated on the flow (Power Automate licensing FAQ). If you already have an app registration, you can use it.

  1. Register an app in Microsoft Entra ID (App registrations > New registration) and give it a client secret. You need its application (client) ID, directory (tenant) ID and the secret.
  2. In the Power Platform admin center, open your environment, then Settings > Users + permissions > Application users > New app user. Pick the app and your business unit, and give it the security role Chrona Workforce Admin.
  3. In Power Apps, open Connections > New connection and select + on the green, round Microsoft Dataverse, as in item 1 of the first list. Select Connect with service principal. Enter the client ID, the secret and the tenant ID. Share the connection with the application user, and bind it on Chrona Scheduled tasks Dataverse in Default Solution, as in item 2 of the first list.
  4. On each of the two flows, select Details > Edit and make the application user the owner. Give each flow a Process licence, or designate a licensed user on it. If the flows are off, turn them on as in item 3 of the first list.

Update to a newer version

Download the newer version from Downloads and import the files you installed again, in their numbered order, as in step 1. Leave the wizard’s choice under Advanced settings on Upgrade, its default. Do not remove the install to update it.

Versions before 0.1.40 are not updated to it: Chrona had no customer installs before 0.1.40.

An update keeps the website’s address and its app user, the connections, the flows that are on and the worker directory settings.

Help

[email protected]

Search documentation

Browse documentation

Choose documentation

Connect your agent to Chrona

Connect Chrona MCP for documentation, setup guidance and configuration recipes.

Server address

https://mcp.chrona365.com/mcp

Streamable HTTP; authentication: None.

In Copilot Studio, after importing Chrona, add the Chrona Scheduler connector to your agent alongside Microsoft’s Dataverse tools.

Your agent needs separately authorized Dataverse tools to apply changes. Connecting Chrona MCP alone does not grant access to your environment.

Ask AI

How can we help?

Ask about Chrona’s setup, features or terminology. Answers link to the documentation they use.

Answers use public documentation. Check the linked sources.