Share

About Flow Generative Scheduling permissions

Several mechanisms are available to help an administrator have control over who can use Flow Generative Scheduling with Flow Production Tracking.

These are summarized the following table and explained in their respective sections.

Sign in GS See GS in App drop-down Connect GS to FPTR Import Schedule from FPTR to GS Export schedule from GS to FPTR Use Apply Proposed Start Date menu option
Have the see the app permission for the GS app X X X X
Have a subscription to Generative Scheduling in account management X X X X
Permissions to edit Proposed Start Date field on Task entity X
Permissions to edit Task entity Start Date, Proposed Start Date, and Pinned X
Permissions to read project data in Flow Production Tracking X X

GS stands for Flow Generative Scheduling, and FPTR for Flow Production Tracking

Access to Flow Generative Scheduling

By default, all users who have a Flow Production Tracking subscription will also have a subscription for Flow Generative Scheduling. This means that they are able to navigate directly to Flow Generative Scheduling and sign in using their Autodesk Account.

Autodesk Primary or Secondary administrators can remove a user's ability to sign in Flow Generative Scheduling by removing their subscription to Flow Generative Scheduling in account management.

manage product access from Autodesk account

For more information on managing users and subscriptions, see the Autodesk account admin Quick Start Guide, especially the Assign access by product video.

See the Flow Generative Scheduling app in Flow Production Tracking

To configure who can see Flow Generative Scheduling in Flow Production Tracking, as an admin, open Manage Apps, in the User Menu.

gs Flow Production Tracking app

The configuration for the Flow Generative Scheduling app contains one setting, Who can see the app? By default, the Admin role is the only role with permissions to see the Flow Generative Scheduling app.

gs Flow Production Tracking app permissions

Who can see the app? controls several aspects of the integration between Flow Generative Scheduling and Flow Production Tracking:

  • Users with this permission can see Flow Generative Scheduling in the Apps menu, and click it to navigate directly to Flow Generative Scheduling.

    gs Flow Production Tracking app dropdown

  • In Flow Generative Scheduling, users that have the see the app permission can:

    • Establish a connection between Flow Generative Scheduling and the Flow Production Tracking site.
    • Import schedules from Flow Production Tracking into Flow Generative Scheduling.
    • Export proposed start dates from a Flow Generative Scheduling scenario back into Flow Production Tracking.

Project & task Permissions

Some aspects of the integration between Flow Production Tracking and Flow Generative Scheduling are controlled by entity permissions in Flow Production Tracking.

For more information on permissions in Flow Production Tracking, see this Permissions article.

Importing a schedule from Flow Production Tracking to Flow Generative Scheduling

Importing a schedule into Flow Generative Scheduling from Flow Production Tracking requires permissions for the specific projects to import.

Users cannot import projects into Flow Generative Scheduling unless they have permissions in Flow Production Tracking to access those projects.

Exporting proposed start dates from Flow Generative Scheduling to Flow Production Tracking

Exporting proposed start dates to Flow Production Tracking requires the user to have permission to edit the Proposed Start Date field on the Task entity.

Applying start dates to tasks in Flow Production Tracking

Using the Apply Proposed Start Date menu option on the Task entity requires that the user has permission to edit the following fields on the Task entity:

  • Proposed Start Date (because this field is cleared by this action)
  • Start Date (because this field is updated with the value of the 'Proposed Start Date' field)
  • Pinned (because the Pinned value will be set to True by this action)

If a user does not have permission to edit all of these fields on the Task entity, they will not see the Apply Proposed Start Date menu option.

Was this information helpful?