Posit Assistant Admin Controls

Workbench | Preview

WarningPreview feature

This feature is in preview. Preview features are unsupported and may face breaking changes in a future release. Any issues found in the feature will be addressed during the regular release schedule; they will not result in immediate patches or hotfixes.

We encourage customers to try these features and we welcome any feedback via Posit Support, but we recommend that the feature not be used in production until it is in general availability (i.e., officially released as a full feature). To provide feedback, please email your Posit Customer Success representative or and specify that you are trialing this feature.

The assistant-enabled key in /etc/rstudio/profiles unifies Posit Assistant control across both RStudio Pro and Positron Pro sessions. Posit Workbench administrators can apply it on a global, per-group, or per-user basis.

Configuring the assistant-enabled profile key

The key takes one of two values:

Value Behavior
1 Posit Assistant is enabled for the matched users/groups.
0 Posit Assistant is disabled and cannot be re-enabled by the user.

The key accepts the same scope syntax as all other profile keys: a global section ([*]), per-group sections ([@groupname]), and per-user sections ([username]). See User and Group Profiles for the full profiles syntax.

Note

The assistant-enabled key only enforces a policy when set. When absent from /etc/rstudio/profiles, it imposes no constraint on Posit Assistant availability.

Example

The following example disables Posit Assistant for all users and then re-enables it for members of the data-scientists group. It also disables access for a specific contractor account:

/etc/rstudio/profiles
[*]
assistant-enabled = 0

[@data-scientists]
assistant-enabled = 1

[jcontractor]
assistant-enabled = 0

More specific sections take precedence: a group section ([@groupname]) overrides global ([*]), and a user section ([username]) overrides any group section. If a user belongs to multiple groups, the file is evaluated top-to-bottom and the last matching group section wins.

Applying changes

After editing /etc/rstudio/profiles, restart Workbench to apply the changes:

Terminal
sudo rstudio-server restart

The updated settings take effect for sessions launched after the restart. Existing sessions keep the configuration they received at launch.

Helm chart configuration

On Kubernetes deployments using the Workbench Helm chart, /etc/rstudio/profiles is managed via config.server.profiles in values.yaml:

values.yaml
config:
  server:
    profiles:
      "*":
        assistant-enabled: 0
      "@data-scientists":
        assistant-enabled: 1

See the Configuration files section of the Helm chart README for the full list of supported config keys and their mapping to files on disk.

Back to top