Federal Science DataHubFederal Science DataHub
  • English
  • Français
  • English
  • Français
  • Overview
  • Managing Workspaces and Users

    • Getting a workspace (only available on the GC network)
    • Estimate costs (only available on the GC network)
    • Account Setup
    • Requesting, configuring and removing tools in your workspace
    • Invite a user
    • Change a user role
    • Manage your CBR & workspace budgets
  • Storage

    • Working with Azure Storage
    • Bring Your Own Storage

      • Import AWS S3 Bucket
      • Import Azure Storage
      • Import Google Cloud Platform Storage
    • Access Storage in Databricks
    • Use AzCopy to Interact with Storage
  • Databricks

    • Getting Started with Databricks
    • FSDH Cluster Policies
    • MLFlow: AutoML and Experiments
    • Databricks Workflows
    • Dashboarding

      • How to Dashboard in Databricks
      • Dashboarding Tool Comparison
    • External Extensions

      • Git/GitHub Integration with Databricks
      • Databricks VS Code Extension
      • Working with Conda
      • Connecting Google API to Databricks
  • PostgreSQL

    • Create and use a PostgreSQL Database
    • Add a User to PostgreSQL on FSDH
    • PostgreSQL vs Azure Databricks Database Features
  • Web Applications

    • Hosting Web Apps on DataHub
  • Migrating to Production

    • Migrating Storage
    • Migrating Databricks
    • Migrating PostgreSQL
    • Migrating Web Apps
  • User Guidance

    • Account Management and Access control of workspaces
    • Backup and Recovery
    • Github and code repo management
    • Incident Detection & Response
    • Monitor Usage
    • Monitoring and Auditing a Workspace
    • Source code
    • Restricted File Types on FSDH Storage
  • Terms and Conditions

Account Management and Access control of workspaces

The account management and access control and ongoing maintenance of workspaces are the responsibility of the departments using the Federal Science DataHub (FSDH). Within the department, the role of access control, account management and ongoing maintenance is the responsibility of the Workspace lead. A departmental user requesting access to the FSDH portal is assigned the role of Workspace lead and their responsibilities, and each user's responsibilities are detailed below:

The following are roles and responsibilities for components within the workspace.

RoleDatabricks RoleWeb Application RoleStorage RolePostgreSQL Role
Workspace leadAdministrators
- Workspace Access
- Databricks SQL Access
- Allow unrestricted cluster creation
- allow-instance-pool-create
Access Configuration, Open web applicationBrowse, Upload, Download, Generate TokenDatabase Access Connection Info
AdministratorAdministrators
- Workspace Access
- Databricks SQL Access
- Allow unrestricted cluster creation
- allow-instance-pool-create
Access Configuration, Open web applicationBrowse, Upload, Download, Generate TokenDatabase Access Connection Info
CollaboratorUsers
- Workspace Access
- Databricks SQL access
Open web applicationBrowse, Upload, DownloadNo role
GuestNo Databricks AccessOpen web applicationNo Storage AccessNo role
Data StewardUsers
- Workspace Access
- Databricks SQL Access
Open web applicationBrowse, Upload, DownloadNo role

The detail roles and responsibilities are in Annex 1 and 2 of the Terms and Conditions.

5.1 Granting access and assigning a role within a workspace

The user is assigned the workspace lead role when they request access to the FSDG portal by completing the request via the Salesforce Portal. The user must agree to the Terms and Conditions and fulfil all funding and policy obligations before granting access. The workspace lead can then assign additional roles by inviting users to the workspace. The users must agree to the Terms and Conditions and meet all departmental policies and requirements associated with their role (for example, Reliability security clearance). In addition, the users must have a valid Government of Canada email account. Workspace lead should consult with their Departmental IT Security authorities to ensure compliance with Access Management requirements established by the Directive on Security Management (Directive on Security Management- Canada.ca - B.2.3.2)

5.2 Managing Access control or account type change

Departments and, specifically, the workspace lead are responsible for notifying if any account/role changes within the workspace occur. If a workspace lead is no longer the lead of the workspace, they are responsible for assigning a new workspace lead.

Note: If the workspace lead abandons the workspace (leaves the organization), all roles within that workspace can submit a support request to FSDH requesting the assignment of a new workspace lead.

In addition, all roles within the workspace are responsible for notifying the workspace lead if:

  • When access is no longer needed or required.
  • Access is changed or no longer needed due to transfer or termination
  • When access privileges are associated with account types or if new account types are created due to a system change or update?
  • When individual workspace usage or need-to-know changes.

The workspace lead is responsible for reviewing the users within its workspace regularly. In the case the access to the workspace (termination of employment, moving projects, departments, etc.) is no longer required for the user. The workspace lead must:

  • Disable FSDH workspace access within two business days.
  • Advise the FSDH team of the termination so that the FSDH team can terminate system-wide access.
Edit this page on GitHub
Last Updated: 2026-04-13, 11:39 a.m.
Next
Backup and Recovery