How can we help?

Gridavera creates its own configuration lists in your SharePoint site during setup. Your existing data lists are not modified — Gridavera reads and writes to them using standard SharePoint APIs.

Gridavera requires:

• User.Read: To identify the signed-in user
• Sites.Selected (or Sites.Read.All): To read/write SharePoint list data
• The specific permissions depend on your chosen write mode (Standard or Secure)

• Standard Mode: The plugin writes to SharePoint using the user’s own token. Simple setup, but users need direct write access to SharePoint lists.
• Secure Mode: All writes are routed through an Azure Function using app-only credentials. Users don’t need direct SharePoint write access, and all modifications are auditable through a single service principal.

Partially. Configuration and authentication are cached locally for a configurable grace period (default 24 hours). Users can open the plugin and see their views, but loading data and submitting changes require an internet connection.

Your data stays in your SharePoint Online environment. Gridavera does not copy or store your business data on external servers. See our Privacy Policy for the limited diagnostic exception. What Gridavera holds in its own backend is your tenant configuration (subscription status, site registrations, roles and per-user access settings) and an activity log of actions taken in the product.

Since your data remains in your own SharePoint Online tenant, it follows your organization’s Microsoft 365 data residency settings. Gridavera’s own backend, which holds your configuration and activity records, runs in the Azure UAE North region.

Yes. Gridavera works with Microsoft 365 guest (B2B) users. To give an external user access, your Microsoft 365 admin adds them as a guest in Azure AD (Microsoft Entra ID) and grants them access to the relevant SharePoint site. Then your Gridavera admin simply adds the guest’s email to the users list with the appropriate roles and dimension filters. The guest will have the same role-based access control as any internal user — they only see the data they are authorized to access.