FAQ
Common questions when getting started with OSDU at Equinor.
Do I need to request platform access?
For all environments (Development, Test, and Production) — No. When you join Equinor, you automatically get read access to these environments through Entra ID. See How to Get Platform Access.
How do I get access to data?
Platform access and data access are separate. To access specific datasets, you need to join the relevant access groups. See Data Access and How to Get Data Access.
What's the difference between platform access and data access?
Platform access lets you call OSDU APIs — search for records, query metadata, and use services. Data access controls which datasets you can actually read or write. You can have platform access without being able to see any data.
How do I get write access?
There are two things you need:
- Platform write access — apply for editor-level access per environment through AccessIT (users) or ServiceNow (apps). See How to Get Platform Access.
- Data owner group membership — contact the Data Office to be added to the owner group for the records you want to modify.
See How to Get Data Access for full details.
How do I get write access to data?
Contact the Data Office — they will add you (or your app's service principal) to the owner group for the records you need. Email dadal@equinor.com (Dag Andre) or elibjo@equinor.com (Eli Bjørnevoll). See How to Get Data Access.
What's the difference between viewer and owner groups?
Every record in OSDU has an ACL with viewer groups (read) and owner groups (write). To read a record, you must be in one of its viewer groups. To write, update, or delete a record, you must be in one of its owner groups.
Can I use my own app registration?
Yes. Each team is responsible for creating and managing their own app registrations. You can create one through the Azure Portal — you need the Application Developer role in Entra ID. Alternatively, reuse an existing one if your team already has one.
Which environment should I use?
Development is for experimentation and pipeline building, Test is for integration and validation, and Production is the stable environment where governed data is made available to the organisation. See Configuration Files for connection details.