Management

Advanced

Workbench within Posit Team is designed to be hands off and includes a robust management page for all day 2 operations that an administrator may want to perform.

Workbench manage page

Workbench manage page

To manage Workbench click the menu icon (vertical dots) on the Workbench card and click manage.

Workbench management page

Workbench management page

Stop and Start Workbench

You can stop or start Workbench at any time. This will suspend the service and compute pool, which will allow for cost savings.

Upgrade Workbench

Note

Posit frequently upgrades the Posit Team Native App, but you control when individual product upgrades are applied. In the future, product upgrades will be automatic if they fall too far out-of-date.

You will see a blue section telling you to upgrade and what has changed. Click the Upgrade button to upgrade Workbench.

Workbench upgrade

Workbench upgrade

Change Configuration

In the management page you can change the license or compute pool sizing. Click Save Changes once you have made changes and refresh the page. If the compute pool or license have changed, an upgrade is required. Follow the upgrade section instructions.

Resizing Compute Pool

Resizing the compute pool takes about 10 minutes to complete.

A compute pool resize causes the Workbench service URL to change. If you have configured Workbench Managed Credentials setup resize the compute pool, you need to update the OAUTH_REDIRECT_URI for the associated Workbench Snowflake security integration.

The following command assumes: - Your application is named POSIT_TEAM adjust POSIT_TEAM_WORKBENCH_OAUTH to have your application name in it - The SPCS Workbench url you have which should look something like ....-<org>-<account>.snowflakecomputing.app

ALTER SECURITY INTEGRATION POSIT_TEAM_WORKBENCH_OAUTH
  SET OAUTH_REDIRECT_URI = 'https://<spcs-workbench-url>/oauth_redirect_callback';

Backup and Restore

Posit Team supports easily creating Workbench backups. Simply specify a backup name or leave it blank for a randomly assigned name and click Save New Backup.

Create backup

Create backup

Next, wait several minutes for the backup to be created.

Backup created

Backup created

Once a backup has been created, you can choose to restore or delete that given backup. Restoring from a backup takes about 10 minutes.

Logs

You can view logs of the currently running Workbench. Currently, a page refresh is required to see newer logs.

Workbench logs

Workbench logs

User Access

In order for Snowflake users to access Workbench their roles need to be given access. We recommend giving the application role POSIT_TEAM_USER to those users.

Snowsight UI
GRANT APPLICATION ROLE POSIT_TEAM.POSIT_TEAM_USER TO ROLE YOUR_USER_ROLE;

To restrict user access to Workbench only give the application role POSIT_WORKBENCH_USER to those users. See Managing Application Roles to learn more.

Snowsight UI
GRANT APPLICATION ROLE POSIT_TEAM.POSIT_WORKBENCH_USER TO ROLE YOUR_USER_ROLE;

Change the egress

To ensure full Native App functionality, key endpoints must be accessible, such as those for Snowflake OAuth and OCSP. For more information, see the security egress traffic documentation.

Editing the default egress policy requires the ACCOUNTADMIN role. You can modify the default egress policy for Workbench by:

  • Using the Snowsight UI (recommended) or
  • Writing your own SQL

To edit network rules via Snowsight UI:

Visit Governance & security -> Network policies -> Network Rules.

Network rule edit

Network rule edit

Edit the given network rule named POSIT_TEAM_APP_DATA.DATA.WORKBENCH_PUBLIC_EGRESS and remember to include the required endpoints detailed in the security egress documentation.

To edit network rules via SQL:

Modify the existing network rule POSIT_TEAM_APP_DATA.DATA.WORKBENCH_PUBLIC_EGRESS.

Snowsight UI
DESCRIBE NETWORK RULE posit_team_app_data.data.workbench_public_egress

--- include custom <host>:<port>
--- host names are allowed
--- this example policy allows all ips on port 80 and 443
ALTER NETWORK RULE posit_team_app_data.data.allow_all_rule SET VALUE_LIST('0.0.0.0:80', '0.0.0.0:443');

Modify the egress rules only after a successful installation, and only change one rule at a time, allowing two to three minutes for each rule to take effect.

Troubleshooting and support

Visit the troubleshooting page for known issues and troubleshooting steps. If none of the troubleshooting steps help, please contact support or click on the Support button in the top right of the screen.

Support link

Support link
Back to top