License types for user access to AR System objects and features
License type | Description |
---|---|
Read | Enables users to create, search for, and display requests within their assigned permissions. Administrators can configure the AR System server to enable users with Read licenses to modify requests that they submit. Users with a Read license can always create requests, similar to Restricted Read. Additional configuration is only required to allow them to modify. |
Fixed | Includes all the capabilities of a Read license, and also enables users (based on the permissions of the groups to which they belong) to modify and save requests that they did not submit. AR System administrators and sub-administrators must have a Fixed license. Other AR System users who consistently need to modify requests must also have Fixed licenses. A Fixed license is associated with a user name and is always reserved for that user. Users who have a Fixed license can access the AR System server at any time. |
Floating | Includes all the capabilities of a Read license, and also enables users to modify and save data for requests that they did not submit, based on the groups to which they belong. Multiple users can use the same Floating licenses, one user at a time: they are available on a first-come, first-served basis. This type of license is designed for users who occasionally need to modify and save requests. When a user who is assigned a Floating license, logs in to AR System, the user is given a Read license. When the user attempts to perform a search, modify, or submit operation, AR System checks for an available Floating license, and the following actions occur:
A license pool consists of a specific number of floating licenses reserved for a group, subject to the number of floating licenses available in the database. When a member of a group logs in, a license from the license pool for that group is granted. When the user finishes using the license, it is released back into the pool. If no licenses are available in the pool, AR System checks if the user is a member of any other group that has a license pool. If no licenses are available in any pool that the user is a member of, a check is made for floating licenses not associated with any pool. A user is never granted a floating license from a pool of which the user is not a member. License pools enable you to give priority to a group that needs licenses more urgently. The group with the smallest group ID has the highest priority. When a non-reserved floating license becomes available, it is granted to the next user who needs it, regardless of the priority of that user's access to the system. For more information about user groups, see Creating-and-modifying-users and User-and-group-access. For more information about application licenses, see Assigning-application-licenses-to-users and Releasing-floating-licenses-to-a-license-pool. |
Restricted Read | Enables users to create, search for, and display requests within their assigned permissions. Users with Restricted Read licenses cannot modify any requests, including their own. Restricted Read licenses enable the same login account to access AR System from multiple IP addresses simultaneously. You can give guest users a Restricted Read license. See Setting-administrative-options. |
Bundled | The following bundled licenses options include a group of licenses that can be assigned to users, which they can use to access the AR System server.
The bundled license option that is displayed, depends upon the license that is assigned to you in the Electronic Product Distribution (EPD) system. |
An AR System server license key activates fixed write licenses, read, and restricted read licenses (which you might have to purchase, depending on your sales contract). You can purchase additional fixed write licenses and floating write licenses from BMC or from an authorized reseller.
The operating system password management system can also be configured to lock out users after too many failed password attempts. Use this method when the user password is stored external to the User form. For more information, see the Max Number of Password Attempts row in the table in Setting-administrative-options. The operating system password management system can also be configured to lock out users after too many failed password attempts. This method is effective where the user password is stored external to the User form.
The following list describes the licenses you can assign to users to access BMC Helix Innovation Suite and its applications:
- Fixed licenses with administrator permissions—The user can access and use BMC Helix Innovation Studio and create and modify codeless applications in BMC Helix Innovation Studio.
- Floating licenses without administrator permissions—The user can access and use BMC Helix Innovation Studio and can access, create, modify, and delete the BMC Helix Innovation Studio application data.
- Read licenses without administrator permissions—The user can access and use BMC Helix Innovation Studio and can access, create, modify, and delete their BMC Helix Innovation Studio application data.
- Restricted read licenses without administrator permissions—The user can access and use BMC Helix Innovation Studio and can access, create BMC Helix Innovation Studio application data. The users cannot modify or delete any BMC Helix Innovation Studio application data.
- Floating, read, or restricted read licenses—The user can use the deployed BMC or Partner applications.
- Fixed licenses with business analyst permissions—The user can access and tailor the BMC Helix Innovation Studio applications.
- Fixed, Floating, or Read licenses—The user can access custom applications. Custom applications do not require any application license.
Where to go from here