Add a new idea Subscribe
Status Planned
Categories Other
Created by Guest
Created on Dec 9, 2020

RELATED IDEAS

Tenant-wide variables

It would be great to be able to configure tenant-wide variables (maybe as a tab in the settings section of the tenant). This would allow creating variables accessible in all forms/workflows that define legal disclaimers or even image urls, so that when updated in this one location chages would be automatically be reflected in all forms.

(Not sure how feesible this is as unsure if the workflows/forms would need to be republished to reflect the variable change).
  • ADMIN RESPONSE
    Sep 7, 2022
    We are looking at addressing this capability, please reach out if you like to find out more as I'd love to discuss how we are planning on approaching and be great for some feedback.
  • Attach files
  • Guest
    Nov 7, 2025

    As a temporary solution:
    I use the Nintex Data Tables now for a similar kind of solution. I store email addresses based on job position titles, which I query in the workflows. Now I only need to change the email address in the data table and it will be dynamically changed in all workflows as they query the data table.

    Reply
  • Guest
    Mar 3, 2025

    It would be great to get an update to this please?

    While we now have nintex tables.

    We still really need the tenant wide variables to replace the old workflow constants for Nintex WF for SharePoint on-prem.

    This also equates to the environment variables that are available within solutions as part of Power Automate.

    Reply
  • Guest
    Sep 7, 2022
    very similar to the nintex sharepoint on-premise workflow constants and is really needed.
    Reply
  • Guest
    Sep 7, 2022
    This seems like something that could be useful for holding temporary authorization tokens that could be shared between workflows/instances. I.E.web services that require getting a bearer token before using further API calls. Could store that token as a tenant-wide variable instead of a workflow-level one and when the token expires you could refresh it only when needed regardless of which workflow the web service is being called from.

    We'd definitely get use out of such a thing. In addition to the probably more common uses of holding reused constants.
    Reply