Hand over a user’s notebooks and files
When a user leaves your organization, you may need to make their notebooks and files available to a new or existing user as part of the offboarding.
There are three ways to transfer the departing user’s notebooks and files to someone else:
(Only with Hub) Change the email associated with the existing account to transfer the whole Datalore account to a different user.
Export the user’s workspaces and import them for another user: transfers notebooks and files, but database connections and SSH keys are not included.
Clone the whole workspace, including database connections.
Option A: Change the user’s email in Hub
Changing a user’s email in Hub automatically updates the respective user’s email in Datalore. It is convenient if you want to transfer the whole account with workspaces, notebooks, files, and data connections to a new user.
After this, the new user can log in with their email and get access to the account.
Option B: Export and import workspaces
Use this option to copy the departing user’s workspace data to a separate Datalore account. Repeat the procedure for every workspace that you need to preserve.
An exported workspace contains workspace attachments, notebooks, and reports made from those notebooks, if available. Sharing settings and scheduled runs are not included in the archive. Database connections and SSH keys are not exported either.
1. (Optional) Ban the departing user
Ban the user whose workspaces you want to hand over.
It prevents them from logging in and accessing workspaces, notebooks, and data but does not release their seat.
2. Export a user’s workspace
In the Admin panel, select Manage users, open the departing user’s profile, and switch to the Workspaces tab.
Open the workspace that you want to transfer. As a Super Admin, you can access the workspace with edit rights.
In the sidebar, click
(Settings) for the workspace.In the Settings dialog, click Download workspace as .zip.
3. Import a workspace
Have the destination user import the workspace from the downloaded ZIP file.
Verify that the imported workspace contains the required notebooks and files.
(Optional) Have the destination user republish the reports, reshare them, and reconfigure scheduled runs.
4. (Optional) Delete the departing user
After you verify that all required data is available to the destination user, you can delete the departing user.
Deleting a user releases the associated seat and permanently deletes all data associated with that user, including notebooks and their published versions.
Option C: Clone the workspace
If you need to copy a workspace with its attached files and database connections, follow the workspace full clone procedure.
This method requires an administrative API token and creates a clone for the destination user. It does not transfer the workspace, and the original remains intact.