Work with geodatabases stored in OneDrive and SharePoint locations
ArcGIS Pro supports storing and working with file geodatabases and mobile geodatabases in Microsoft OneDrive when protected access is enabled. Protected access is an ArcGIS Pro capability that manages access to projects and data to prevent simultaneous editing by multiple users and ensure data integrity.
Learn more about using ArcGIS Pro with Microsoft OneDrive
Unlike other protected file types, geodatabases are not single files that are edited independently. A geodatabase is a workspace that can contain many related datasets and supporting information, such as the following:
Feature classes
Feature datasets
Tables
Relationship classes
Domains
Subtypes
Although users often work with individual tables, feature classes, or feature datasets, ArcGIS Pro manages protected access at the geodatabase workspace level.
Note:
To prevent simultaneous editing and ensure data integrity, protected access for Microsoft OneDrive files must be enabled on each computer that accesses projects and data stored on OneDrive. Protected access is an application setting managed by administrators.
Supported geodatabase workspaces
Protected access applies to the following geodatabase workspaces:
File geodatabases (
.gdb)Mobile geodatabases (
.geodatabase)
Note:
Shapefiles stored in Microsoft OneDrive are also a protected file type.
File geodatabases
File geodatabases are managed as a single workspace when protected access is enabled.
This behavior reflects the way file geodatabases are designed. A file geodatabase is a collection of related files that work together as a single workspace and is stored in a folder with a .gdb extension. Managing access at the workspace level helps maintain consistency across those files and helps prevent simultaneous modifications by multiple users.
The process of checking out and checking in OneDrive items is managed by ArcGIS Pro through a status file associated with the item. For file geodatabases, it is a file named cloudStatus that is stored in the geodatabase folder.
Caution:
Do not modify, rename, move, or delete the cloudStatus file.
For more information, see File geodatabases and protected access.
Mobile geodatabases
As with file geodatabases, mobile geodatabases are managed as a single workspace when protected access is enabled.
A mobile geodatabase is stored in a single SQLite database file with a .geodatabase extension. Managing access at the workspace level helps maintain consistency across the geodatabase and prevents multiple users from editing the same workspace simultaneously.
Mobile geodatabases also create temporary SQLite files during editing operations. These files support locking, transaction processing, and workspace access. They are managed automatically by ArcGIS Pro and should not be modified manually.
The process of checking out and checking in OneDrive items is managed by ArcGIS Pro through a status file associated with the item. For mobile geodatabases, it is a file named <mobile geodatabase name>_geodatabase.status that is stored in the same folder as the mobile geodatabase file.
Caution:
Do not modify, rename, move, or delete the _geodatabase.status file.
For more information, see Mobile geodatabases and locking processes and Mobile geodatabases and protected access.
Geodatabase workspace behavior
ArcGIS Pro does not check out feature classes, tables, or other datasets in a protected geodatabase. Instead, check out applies to the entire workspace. When a protected file geodatabase or mobile geodatabase is checked out, other users can access datasets in a read-only state until the workspace is checked back in. Editing operations and geoprocessing operations that modify data cannot be performed while the workspace is checked out to another user.
If a user checks out a geodatabase and edits data, the geodatabase becomes unavailable to other users and cannot be accessed even in a read-only state. The unavailable status persists until the geodatabase is checked in and changes are synced to the cloud.
Geodatabases are checked out when ArcGIS Pro performs operations that require access to the geodatabase workspace. For example, adding a feature class to a map checks out the geodatabase workspace if it is not already checked out by another user.
Additional examples include the following:
Opening maps with layers or tables that reference geodatabase datasets
Running geoprocessing tools that use geodatabase data or that write output to a geodatabase
Editing geodatabase content
Protected access preserves the existing geodatabase access model by allowing one user to make changes while preventing simultaneous modifications by multiple users. It does not provide concurrent editing capabilities for file geodatabases or mobile geodatabases, nor does it convert these workspaces into multiuser editing systems.
Tip:
For workflows that require concurrent access and editing by multiple users, an enterprise geodatabase is generally the recommended data storage solution because it is designed specifically for multiuser editing workflows. For shared project collaboration in an ArcGIS Enterprise environment, portal projects are the recommended approach.
Learn more about the different ways to distribute data in ArcGIS
Depending on how the workspace is being used, the following are examples of common actions in which a check-in of protected items may occur:
Datasets are removed from maps.
Editing operations are completed.
Open attribute tables are closed.
Open data design views are closed.
The project is closed.
Editing and schema changes
Protected access applies to both data edits and schema modifications. Users with write access can perform tasks such as the following:
Edit features
Update attributes
Modify metadata
Add or delete fields
Create or delete datasets
Modify dataset structure
Determine who has checked out a geodatabase
The Protected Access Status pane provides information about the current status of protected datasets. You can use it to do the following:
See whether a geodatabase is checked out
Identify who currently has the geodatabase checked out
Review recent check-out and check-in activity
See whether a geodatabase is available only in a read-only state or is unavailable.
Planning shared data workflows
When planning shared workflows, consider how datasets are organized within geodatabases. Since protected access applies to the entire geodatabase workspace, datasets that are frequently edited by different users may be easier to manage when stored in separate geodatabases rather than in a single workspace. Organizing data in this way can help reduce situations in which one user's work limits write access to unrelated datasets.
Protected access does not change how geodatabases store or manage data. Instead, it extends existing geodatabase access behavior to supported files stored in Microsoft OneDrive. Continue to organize data based on editing requirements, sharing patterns, and workflow needs.