After you create your GCP billing account or receive permission from your research team to use an existing one, you’ll complete a couple of tasks to set up for use within the All of Us Researcher Workbench. If you haven’t set up your GCP billing account yet, you’ll need to do that first.
Linking your GCP billing account to the Researcher Workbench
Who needs to complete this step?
The individual designated as “billing administrator” permissions for your GCP billing account, and/or the individual who will manage the billing pod in the Researcher Workbench may complete these steps. It is possible for your billing administrator to be someone other than a Researcher Workbench user depending on your GCP billing account set up.
- If you created the account yourself, this should be you.
- If you are using an account managed by your department or institution, check with your department administrator to confirm who is in this role.
- Read about Google role permissions.
To link your GCP billing account to the Researcher Workbench
Once your GCP billing account is established, you will need to grant permission to the workbench to use the billing account for connection to pods and workspaces.
Steps to complete in GCP Billing Console
- Log in to GCP Billing Console.
- Select the billing account to be used.
- Choose “Account Management” on the left hand panel.
- Navigate to “My Billing Account” on the right hand panel.
- Select “Add Principal.”
- Add billing@workbench.verily.com as a "Billing Account User" and save.
- Note: Adding this username as “billing user” on your GCP account only allows for a connection between the Researcher Workbench platform and user accounts to be made. It does not grant view access to the payment or project details of your GCP account. Read about how Google uses role-based permissions to manage billing.
Steps to complete in Researcher Workbench
- In the Researcher Workbench, select your profile > “Linked accounts”
- Select “Link Account” under the Google section.
- This will bring up a dialog window. You will need to sign in with your @researchallofus.org username and check the "View and manage your Google Cloud Platform billing accounts" box.
-
Allow Verily Workbench access to the GCP account.
Creating a billing pod in the Researcher Workbench
Who needs to complete this step?
This step should be completed by the Researcher Workbench user who will be managing the pod as the pod administrator. Pod administrators are able to add:
- Create workspaces with the pod
- Add or remove users from the pod
- Edit pod details
- Delete the pod
Pod administrators are able to add pod users to each pod. Pod users can:
- Create workspaces with pod
- View pod details
When you create a workspace in the Researcher Workbench 2.0, you will be prompted to select a pod. Billing pods are created and linked to a Google Cloud Platform billing account. Consider a billing pod as the GCP billing account.
-
Navigate back to the Researcher Workbench landing page. Select “Pods” on the left hand menu.
-
On the next page, select “New Pod” on the upper right hand side.
-
Enter in the appropriate information related to the GCP billing account for this pod. Then select “Create Pod.”
- After pod creation, you can view your new pod under the “Pods” page. This page will show both the pods that you have created, and those to which others have granted you access.
- You can now use the pod when creating new workspaces.
Billing is managed at the workspace level. Note: Once you select a billing pod for the workspace, it cannot be changed. You will be required to duplicate the workspace to add a new billing pod.
|
|
Disabling your GCP billing account
Who needs to complete this step?
Someone with “billing administrator” or pod admin permissions for your GCP billing account.
- If you created the account yourself, this should be you.
- If you are using an account managed by your department or institution, check with your department administrator to confirm who is in this role.
- Read about Google role permissions.
Where is this step completed?
These steps are completed in the GCP Console Billing and Researcher Workbench
To disable your GCP billing account to the Researcher Workbench
Billing is managed at the workspace level. In GCP billing terms, workspaces are referred to as “projects” and are listed that way in your GCP billing account console.
To fully remove permission for a researcher to bill for existing and future work, you’ll need to remove both the account and existing workspace projects from the GPC account in the GCP billing console.
To remove a GCP billing account entirely from the Researcher Workbench
- Log in to GCP Console Billing.
- Select the billing account to be used.
- Click “Manage” in the top right next to "Billing account."
- Navigate to the Role/Principle list.
- Expand the section header labeled “Billing Account User.”
- Use the edit icon to remove the “billing@workbench.verily.com" account for which no future billing permissions are allowed.
Note - once a valid GCP billing account is removed from a workspace or project, stored cloud resources such as workspace buckets may be deleted.
To remove access to a billing pod in the Researcher Workbench
If you are a pod admin in the Researcher Workbench, you can remove user access to a pod by the following:
- Navigate back to the Researcher Workbench landing page. Select “Pods” on the left hand menu.
- Select the billing pod of your choice
- Click “Permissions”, which will display a page with a full list billing pod users and admins.
- Select the three dots on the right hand side of the user name > 'Remove'
Note: Workspaces will continue to incur a charge of $0.20 a month through the billing account unless they are deleted inside the Researcher Workbench. Applications that are left running when a project gets disabled will continue to charge until the application is turned off and data stored in a workspace bucket will continue to incur costs.
As a best practice when disabling projects, researchers should log in to the Researcher Workbench, delete projects they no longer need, and ensure no applications are accidentally running.
Comments
0 comments
Article is closed for comments.