FAQ
Common questions when getting started with OSDU at Equinor.
Do I need to request platform access?
For dev and test — no. When you join Equinor, you automatically get read access to these environments through Entra ID. For production, you need to apply for read access through AccessIT — see the step-by-step guide.
How do I get access to data?
Platform access and data access are separate. To access specific datasets, you need to apply for the relevant access groups via AccessIT. See Getting Access to Data for the full guide.
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 — you need editor-level service access. Follow the step-by-step guide on ServiceNow: How to get write access to ADME.
- Data owner group membership — you need to be in the owner group for the specific records you want to modify.
See Getting Access to Data for full details.
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 Equinor's Omnia Radix portal, or reuse an existing one if your team already has one.
Which environment should I use?
The intended use of each environment (dev, test, prod) is to be determined. All three environments are available to all Equinor users. See Configuration Files for connection details.