Uploaded image for project: 'Atlassian Access'
  1. Atlassian Access
  2. ACCESS-1185

Allow non-billable policy to override the provisioning feature.

    XMLWordPrintable

Details

    • 22
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    Description

      At the moment, provisioning is a paid feature in Atlassian Access. We provide a non-billable policy but one limitation is that we cannot set a provisioned user as non-billable policy member.

      To make a provisioned user non-billable, the integration (directory) needs to be recreated and the non-billable users should be removed from the provision scope before the initial sync. They can then be added to the non-billable policy

      Suggestion

      Allow for non-billable policy to override the provisioning feature.

      • Do not sync an account that is non-billable
      • Break the sync status of an account that is set to non-billable.

      Attachments

        Issue Links

          Activity

            People

              e902c0832f88 Sudesh Peram
              rmacalinao Ramon M
              Votes:
              23 Vote for this issue
              Watchers:
              29 Start watching this issue

              Dates

                Created:
                Updated: