Administrator Account Features settings

As an administrator, use Account Features in the Settings menu to configure user access controls for various features on your account.

Advanced Environment Access

Enabling the Advanced Environment Access feature allows account administrators to customize access controls at the environment level.

Details

There are several settings that account administrators can apply to make their environments more secure and accessible for their account users.

• Environment Management Read Access— when a custom role with this privilege is created and assigned to a user in Settings > *Account Access > User Management and then assigned to a specific environment in Manage > Runtime Management, users with the custom role can view (but not edit) information in the environment. This may restrict access to an environment for users with the Runtime Management privilege.

• Environment Management Full Access— when a custom role with this privilege is created and assigned to a user Settings > Account Access > User Management and then assigned to a specific environment in Manage > Runtime Management, users with the custom role can both view and edit information in the environment. This may allow users to access certain environments, but can not elevate priviledges for a user without the Runtime Management privilege.

  note

  It is highly discouraged that administrators assign both Environment Management and the Environment Management Full Access privileges simultaneously; the Environment Management privilege overrides both Full Access and Read-Only roles. When assigning roles, it is important to note that the Runtime Management option is necessary because Advance Environment privileges alone aren't enough. The runtime management option with the most restrictive settings will apply to the environment even if one of them has the full access option. For example, if you apply Runtime Management at Full Access but you have Environment Access at Read Only for a particular environment, within that environment, settings will behave as if you have Read Only access.

To leverage this feature once it has been enabled in Settings, the administrator needs to do the following:

1. Navigate to Settings > Account Access > User Management to create custom roles with both or either Environment Management Read Access or Environment Management Full Access privileges.

2. Assign these new custom roles to users of the account.

3. Finally, navigate to Manage > Runtime Management, select an environment, and add the newly create custom roles in the Roles With Access field as desired.

   By doing this, the administrator specifies that the environment can be edited by those users assigned with the Full Access role, or viewed by those users assigned with the Read-Only role.

When the Advanced Environment Access feature is toggled ON, it enforces the read and write custom roles configured on the environment, and user's access is displayed as labels on each environment tile within the Runtime Management page. After assigning roles to both users and environments, standard users who are currently logged into the platform notice changes upon a page refresh; otherwise, users notice changes the next time they log in.

If the Advanced Environment Access toggle is toggled OFF, the account configuration assumes the Environment Management privilege only (if applied), and access controls cannot be applied on a per environment basis.

Consider this sample configuration to manage a production and development environment.

Roles

• Developer role:

  • Runtime Management privilege
  • Build
  • Packaged Component Deployment
  • Packaged Component Management

• Production View role:

  • Environment Management - Read Only privilege
  • View Data
  • View Results

• Production Engineer role:

  • Runtime Management
  • Environment Management - Full Access privilege
  • View Data
  • View Results

Environments

• Development Environment

  • Accessible by Developer Role

• Production Environment

  • Accessible by Production View role
  • Accessible by Production Engineer role

Consider a user with both the Developer role and the Production View role. This user would have full runtime management within the Development environment, including the ability to deploy new packages, update schedules, update extensions, and execute processes. However in the Production environment, the Environment Management - Read Only privilege would restrict their access. They would be able to view schedules, process properties, and extensions but not modify any of them. They would be able to review the results and logs of executions in production, but not launch new executions.

Compare this to a user with only the Production Engineer role. This user would have full access to the Production environment, including updating schedules, updating extensions, adding and removing attachments, and executing processes manually. However this user would have no visibility into the Development environment and no ability to deploy new processes to the Production environment. That would require a user with both the Developer and Production Engineer roles, who would have full access to both environments.

This is one example for how to manage these privileges, but certainly there are many possible valid configurations. For example, the Production View role might want specific privileges to schedule or execute processes.

Branching and Merging

Boomi's Parallel Development with Branch and Merge feature allows you to create, manage, and merge development branches. This advanced versioning capability not only helps you minimize disruptions to production components, but enables multiple developers to work seamlessly in the same account.

You can manage branches in the Boomi Enterprise Platform or by using the Branch and Merge Request API objects. You cannot disable Branch and Merge after enabling it. Contact your Boomi Account representative if you want this feature disabled.

Details

Only account administrators can enable the Branch and Merge feature in an account. From the Features page (Settings > Account Access > Features), toggle on the Branching and Merging feature. To learn more about how you can use this feature, refer to Parallel Development with Branch and Merge.

Component Locking

When you enable component locking for an account, users cannot edit components locked by other users unless they have the Administrator role. Component locking is available to all accounts, but is not turned on by default. To learn more about how you can use this feature, refer to Component locking.

License Enforcement

Enable or disable deployment locking when your account has met the available connection count limit. Contact a Boomi sales representative to purchase a higher license count.

Data Collection

Data Collection allows Boomi to utilize the statistical data and information gathered during your regular use of the Platform to help us improve the future development of our product features and updates. By opting in to Data Collection, you benefit through the following capabilities:

Details

• Recommended filters when building connector Query operations.
• Recommended fields when building maps (Boomi Suggest).
• Recommended solutions to troubleshoot and fix document or process errors (Resolve Agent).

When the Data Collection feature is toggled ON, you allow your Boomi account data to be transmitted electronically to Boomi, authorize us to retain and use the information when developing future generally available product features and updates, and use the data for Boomi-internal analytics reporting.

If the Data Collection feature is toggeld OFF, your product functionality is not affected. However, Boomi cannot consider your data when developing future product features and updates. Furthermore, your account does not participate in, nor does it benefit from the features. Any data that has already been collected for your account will be removed in 24 hours. If you opt back in before the data is removed, the data is not removed.

info

If your account is opted in to Data Collection when it should not be, opt out by toggling the Data Collection setting to OFF. This setting is only available to account administrators. If you are an account administrator and do not see the option, contact your Boomi account administrator. After verifying your identity, administration users then contact Boomi Support on your behalf. Allow Support up to two business days to opt your account out of Data Collection.

RSS Feeds Access

Dynamically enable or disable user access to Boomi RSS feeds on an account. When RSS Feeds Access is disabled for a user, the user is unable to view RSS Monitor Feed and RSS Alerts Only Feed links on Settings and Runtime Management pages.

Users who previously subscribed to Boomi RSS feeds prior to disablement will no longer receive updates. Attempting to access RSS feeds through the Platform API results in an error message that reads "Access to RSS Feeds is disabled on this account." RSS feeds are off by default for new users.

API Lifecycle

Advanced versioning and service lifecycle management for your APIs.