Reference data that meets your governance bar.

Row-level security means each user sees only the rows in a registry that they are allowed to see, even when several teams share the same registry. For example, the finance team sees cost center codes while operations sees product codes. gridmap applies the filter on the server, so there is no need for separate files or spreadsheet tabs. Once it is set up, it works on its own.

gridmap uses role-based access control with user groups. You add users to groups (for example "Finance editors" or "Operations viewers") and grant read, write or admin access per project, gridmap or registry, with row-level rules on top. Changes take effect immediately. You can also sync row permissions from a user table in your data warehouse.

The activity log records who opened a gridmap or registry, who changed which value, who imported or synced data, who granted or revoked access, and when. Edits keep both the previous value and the new value. You can filter and search the log, and export it to CSV for compliance reviews.

Database connection credentials are encrypted with Fernet symmetric encryption before they are stored. Connections to your databases use TLS by default.

Yes. gridmap supports single sign-on with Microsoft Entra ID and Google on the Professional and Enterprise plans. People from your allowed email domains can get an account on their first sign-in, with or without admin approval. Multi-factor authentication (authenticator app or passkey) is required for admins and available to every user.

You sync a control registry from a table of emails and permission values in any supported database. gridmap uses that registry to decide which rows each person sees, and someone with several rows gets access to all of their values. Sync it on a schedule and access keeps up as your team changes.

gridmap runs on Microsoft Azure in the Sweden Central region, and data at rest is encrypted. Access is logged, and row-level security limits data to the people allowed to see it. On the Enterprise plan your data can stay in your own PostgreSQL database. If you use AI mapping, the values being mapped are sent to the AI provider. For specific compliance requirements, contact us for details on our data processing agreements.

Yes, on the Enterprise plan. gridmap stores your data in your own PostgreSQL database: self-hosted PostgreSQL, Azure Database for PostgreSQL, Amazon RDS or Aurora PostgreSQL, or Google Cloud SQL for PostgreSQL. Your database holds gridmap values, registry rows, their change history and audit trail, comments, value lists and uploaded import files. gridmap keeps only configuration: users, projects, the structure of your gridmaps and registries, access rules, schedules and connection settings. An admin sets it up under Targets. gridmap needs a database user that can write to one schema, and admins get step-by-step grant scripts. If you use AI mapping, the values being mapped are still sent to the AI provider.