vania-janet/multiturn-rag-retrieval-data huggingface dataset:
[External link icon](https://cloud.ibm.com/docs-content/v1/content/icons/launch-glyph.svg)](https://www.ibm.com/support/knowledgecenter/SSQP8H/iot/platform/roles_index.htmluser_roles).
* Column 3: The ISO 6801 date (for example, 2018-03-13) that corresponds to the user expiry date.









 Editing users 

Users can be edited to change their role, add, remove, or change an access expiration date, or add or remove access to the organization.



1. In your Watson IoT Platform dashboard, click Members from the navigation bar.
2. Click the Edit icon next to the user you wish to edit.
3. Make the desired changes to the user.
4. Click Save.







 Blocking user access 

Users can be blocked from accessing the Watson IoT Platform organization, while still maintaining organization membership.



1. In your Watson IoT Platform dashboard, click Members from the navigation bar.
2. Click the toggle next to the user you wish to block from accessing the Watson IoT Platform organization.







 Limiting user access 

Resource-level access control enables you to limit access to devices in an organization. You can use resource groups to specify the devices that each user or API key can manage. For information on how to configure resource-level access control, see [Configuring resource-level access control ![External link icon](https://cloud.ibm.com/docs-content/v1/content/icons/launch-glyph.svg)](https://www.ibm.com/support/knowledgecenter/SSQP8H/iot/platform/reference/rlac.htmlconfigure_RLAC).





 Removing users 

Users can be removed entirely from the Watson IoT Platform organization.
* Continuous Delivery: delete auth-user [service name] (auth-user(s): [EMAILS]; root-action: [ACTION]; root-action-service-instance: [CRN])



Where:



* [EMAILS] is a comma-separated list of the user email IDs that are added to or removed from the list of authorized users.
* [ACTION] identifies the action that prompted the automatic addition or removal of user emails from the list of authorized users. If a root-action is not specified, the addition or removal of the user emails was performed directly by a user from the Manage tab of the Continuous Delivery service dashboard.
* [CRN] specifies the [Cloud Resource Name](https://cloud.ibm.com/docs/account?topic=account-crn) of the resource to which the root-action was applied. This resource can either be a toolchain or the Continuous Delivery service instance itself.



The following table lists and describes the root actions that prompt user emails to automatically be added to or removed from the authorized users list.



Table 8. Actions that add or remove user emails from the authorized users list

 Root action Description 

 continuous-delivery.instance.create Add a user email when the Continuous Delivery service is provisioned. This email belongs to the user who created the service instance. The root-action-service-instance CRN identifies the Continuous Delivery service instance. 
 continuous-delivery.instance.delete Remove user emails when the Continuous Delivery service is de-provisioned. The root-action-service-instance CRN identifies the Continuous Delivery service instance. 
 toolchain.git-repos-and-issue-tracking-repo.evaluate Add user emails after system evaluation of a Git Repos and Issue Tracking repo. Multiple emails that correspond to users with Developer (or greater) access to the repo might be added. The root-action-service-instance CRN identifies the toolchain that contains the Git Repos and Issue Tracking tool integration. 
 toolchain.pipeline-stage.start Add user emails when a delivery pipeline stage starts. If the pipeline stage is manually started, the email of the user who started the pipeline is added.
Click the vertical overflow menu next to the Status column, and then click Migrate instance to account.
5. In the Migrate instance to account window, confirm the account to migrate the instance to, and then click Migrate.







 Results 



1. You get a console notification that your request to migrate the instance to the specified IBM Cloud account is accepted.
2. When the instance migration is completed, the instance is displayed on the Resources page under the account to which it was migrated. The migrated instance is no longer displayed in the original account from which it was migrated.







 Related links 



* [Managing user access with IAM](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-iamiam)
* [Inviting users to access services and resources](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-useraccountuseraccount-iamuserinv)
* [How IBM Cloud IAM works](https://cloud.ibm.com/docs/account?topic=account-iamoverview)
* Check the box for the corresponding custom role that you set up in [Step 1](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-grant-pkcs11-ui-accessstep1-create-custom-roles-pkcs11-ui) based on your needs.



If you don't have any custom roles, you can select the existing IAM roles that cover the actions that you want to assign to the user. You can view the specific actions that correspond to the role by clicking the number.
8. (Optional) Under Conditions (optional), click Review to check the access policy.
9. After confirmation, click Add > Assign.







 What's next 

Continue to read [Managing EP11 keystores with the IBM Cloud console](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-manage-ep11-keystores-ui) and [Managing EP11 keys with the IBM Cloud console](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-manage-ep11-key-ui) on detailed operations.
Expand the Devices category and select View Hardware Details and OS Reloads and Rescue Kernel.
6. Click Apply.





 Adding specific device-level permissions 

If you want to provide a user access to a specific device, complete the following steps.



1. Log in to the [Access (IAM)](https://cloud.ibm.com/iam/users) page in the IBM Cloud® console.
2. Select View: My classic infrastructure users.
3. Select a user, then click the Classic infrastructure tab and the Devices tab.
4. In the Select type section, select All bare metal servers to allow users to access all the bare metal devices.
5. In the Enable future access section, select Auto bare metal server access to grant the user permanent access to any newly added bare metal device.
6. Use the devices table to grant a user access to specific, individual devices.
7. Click Set.



In order to see specific devices, you must already have the correct permissions enabled on the permissions tab. If you do not, no devices will be listed.







 Next steps 

User permissions are updated immediately after the changes are submitted. If permissions are granted, the user can view or interact with the selected features. If permissions are removed, the user can no longer view or interact with the selected features. Permissions can be updated again at any time.
[Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/checkmark-icon.svg) 
 Assign access to others ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/checkmark-icon.svg) 
 Update the account owner ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/checkmark-icon.svg) 
 View all users ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/checkmark-icon.svg) 
 Set user visibility !
For more information about the actions associated with each role, see [Actions and roles for account management services](https://cloud.ibm.com/docs/account?topic=account-account-servicesaccount-management-actions-roles).







 Step 4: Invite team members to your account 

After you create the Example Corp Virtual Server Image access group, you're ready to invite team members to your account and add them to your access group. Team members are granted the following editor permissions by default:



* Partner Center - Sell: Complete onboarding tasks, update the visibility of products at the account level, and request approval to publish products to the IBM Cloud catalog.
* Private catalog: Onboard products to private catalogs, update the visibility of products at the account and private catalog levels, and restrict the visibility of products in the IBM Cloud catalog.





1. Click Invite in the Invite team members section.
2. Select the user type:



* Business: A team member who can provide certain details, such as the product logo, description, and customer support experience.
* Technical: A team member who can import the product to your test environment, configure the deployment details, and validate it's ready for use.



3. Enter the email address of each team member.
4. Click Invite.







 Next steps 

You're ready to start the onboarding process. In the Onboard your product section, click Let's go, and [define the product details the virtual server image for Power Systems](https://cloud.ibm.com/docs/sell?topic=sell-vsipower-define).
The following dialog will appear. Click Close

Zoom

![MAS-MS-Register-Request-Sent](https://cloud.ibm.com/docs-content/v1/content/bd177462727ef0a849ddcf8c842a6203b41f0625/mas-ms/images/MAS-MS-Register-Request-Sent.png)

Figure 13. MAS-Dedicated Request Sent
9. An email notification will be sent confirming your request:

Zoom

![MAS-MS-Register-Request-Sent-Confirm](https://cloud.ibm.com/docs-content/v1/content/bd177462727ef0a849ddcf8c842a6203b41f0625/mas-ms/images/MAS-MS-Register-Request-Sent-Confirm.png)

Figure 13. MAS-Dedicated Request Sent Confirmation

Note: Once you request has been submitted, please be patient. It will take some time (up to 24 hours) for IBM to review and approve your request.

To confirm your access, login with your IBMid to the Support Access page:

[https://www.ibm.com/mysupport/s/supportaccess](https://www.ibm.com/mysupport/s/supportaccess)

You should see your product access with a Status of ‘Approved’ under your ACCOUNT:

Zoom

![MAS-MS-Register-Request-Approved](https://cloud.ibm.com/docs-content/v1/content/bd177462727ef0a849ddcf8c842a6203b41f0625/mas-ms/images/MAS-MS-Register-Request-Approved.png)

Figure 13. MAS-Dedicated Request Approved

If you need support, see the next section How to Create a Case







 How to Create a Case 

This section describes how to create a case for Maximo Application Suite Dedicated (MAS-Dedicated)



1.
<br> Start the forgot password email flow for a Cloud Directory user.<br> * Check whether the forgot password email was successfully sent.<br> * Resend an email to a Cloud Directory user.<br> * Start the change password email flow for a Cloud Directory user.<br> * Update your email template configuration.<br> * Delete an email template configuration.<br> * Set Cloud Directory email sender details configuration.<br> * Update a user profile with the information from your application.<br> * Create a new Cloud Directory user.<br> * Update a Cloud Directory user's information.<br> * Delete a user from Cloud Directory.<br> * Update a user profile.<br> * Create a future user.<br> * Revoke a users refresh token.<br> * Register a new app with App ID.<br> * Update an app that is registered with App ID.<br> * Delete an app that is registered with App ID.<br> * Configure or update your own email provider.<br> * Test your email provider configuration.<br> * Update your auditing status.<br> * Update an MFA channel.<br> * Update your MFA configuration.<br> * Update your Cloud Directory SSO configuration.<br> * Initiate SSO logout for Cloud Directory.<br> * Test your MFA configuration for SMS.<br> * Remove Cloud Directory users and their profiles.<br> * Update your rate limit configuration.<br> * Add a scope to an application.<br> * Get the scopes that are associated with an application.<br> * Delete a scope that is associated with an application.<br> * Add a role.<br> * Update the roles in your instance of App ID.<br> * Delete a role.<br> * Update the roles that are assigned to a specific user.<br> * Update the status of a registered extension for an instance of App ID to enabled or disabled.<br> * Update a registered extension's configuration.<br> * Test a registered extensions configuration.<br><br><br>
In the console, go to Manage > Access(IAM).
2. Click Users from the left navigation pane.
3. From the row for the user that you want to assign access, select the Actions menu, and click Assign access.
4. Click Access policies and select VMware Solutions from the Service table. Then, click Next.
5. Select the resource to receive access and click Next.



* Click All resources to grant access to all service resources.
* Click Specific resources and select the attribute type, operator, and value.



6. Select any combination of roles and click Review to review all of your selections.
7. Optionally, click the Edit icon ![Edit icon](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/icons/edit-tagging.svg) to update any of your selections.
8. Click Add and click Assign.



To grant user permission to create new instances for VMware Shared, you must also assign Resource Group access policies. For more information, see [Giving access to resources in resource groups](https://cloud.ibm.com/docs/account?topic=account-rgs_manage_access) and [Ordering virtual data center instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-shared_ordering).







 Managing access for users 

You can add new users to the IBM Cloud account so that these users can share the services and resources that are provisioned for the account. For more information, see [Inviting users to access services and resources](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-useraccountuseraccount-iamuserinv).

You can also manage the access for existing users, including modifying existing access, assigning new access, and reviewing assigned access. To manage access for users, you must be the account owner or you must have the Administrator platform management role.
[Shows the Manage handlers link on the node with slots](https://cloud.ibm.com/docs-content/v1/content/417db917d18067d9dcc4cf2612564a9a87c3ddc8/assistant/images/slots-manage-handlers.png)
4. Add the following values to the fields.



Node-level handler details

 Condition Response Action 

 `#exit` Ok, we'll stop there. No reservation will be made. Skip to response 



The Skip to response action jumps directly to the node-level response without displaying the prompts associated with any of the remaining unfilled slots.
5. Click Back, and then click Save.
6. Now, you need to edit the node-level response to make it recognize when a user wants to exit the process rather than make a reservation. Add a conditional response for the node.

From the edit view of the node with slots, click Customize, set the Multiple conditioned responses switch to turn it On, and then click Apply.

![Shows the Multiple responses toggle after it is turned on](https://cloud.ibm.com/docs-content/v1/content/417db917d18067d9dcc4cf2612564a9a87c3ddc8/assistant/images/slots-multi-responses.png)
7. Scroll down to the response section for the node with slots, and then click Add response.
8. Add the following values to the fields.



Node-level conditional response details

 Condition Response 

 `has_skipped_slots` I look forward to helping you with your next reservation. Have a good day. 



The has_skipped_slots condition checks the properties of the slots node to see if any of the slots were skipped. The exit handler skips all remaining slots to go directly to the node response. So, when the has_skipped_slots property is present, you know the exit intent was triggered, and the dialog can display an alternate response.
For more information about the actions associated with each role, see [Actions and roles for account management services](https://cloud.ibm.com/docs/account?topic=account-account-servicesaccount-management-actions-roles).







 Step 4: Invite team members to your account 

After you create the Example Corp Terraform Template access group, you're ready to invite team members to your account and add them to your access group. Team members are granted the following editor permissions by default:



* Partner Center - Sell: Complete onboarding tasks, update the visibility of products at the account level, and request approval to publish products to the IBM Cloud catalog.
* Private catalog: Onboard products to private catalogs, update the visibility of products at the account and private catalog levels, and restrict the visibility of products in the IBM Cloud catalog.





1. Click Invite in the Invite team members section.
2. Select the user type:



* Business: A team member who can provide certain details, such as the product logo, description, and customer support experience.
* Technical: A team member who can import the product to your test environment, configure the deployment details, and validate it's ready for use.



3. Enter the email address of each team member.
4. Click Invite.







 Next steps 

You're ready to start the onboarding process. In the Onboard your product section, click Let's go, and [define the product details of your Terraform template](https://cloud.ibm.com/docs/sell?topic=sell-terraform-template-define).
* By submitting the order, the client agrees to these terms and thus grants consent to IBM Support to access their instances at any time without prior notification to swiftly resolve issues that pertain to the environment or to prevent future failures.
* This consent applies to all instances currently being ordered throughout their lifecycle. Instances and instance components that are provisioned in the future might require extra consent.







 Steady-state operations 

If the client does not grant consent to proactive support for an instance in the initial provisioning and ordering, they must include explicit consent in any future service tickets, if wanted. Statements of consent must follow the set guidelines or are considered void.





 Related links 



* [vCenter Server overview](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_vcenterserveroverview)
* [Contacting IBM Support](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-trbl_support)
[Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/checkmark-icon.svg) 
 Set user visibility ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/checkmark-icon.svg) 
 Billing responsibility ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/checkmark-icon.svg) 
 Owner notifications ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/checkmark-icon.svg) 
 Default email ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/checkmark-icon.svg)
[Shows the Manage handlers link on the node with slots](https://cloud.ibm.com/docs-content/v1/content/a2b18c153837bce00a5b4de496e4b4ca64bbf56e/assistant-data/images/slots-manage-handlers.png)
4. Add the following values to the fields.



Node-level handler details

 Condition Response Action 

 `#exit` Ok, we'll stop there. No reservation will be made. Skip to response 



The Skip to response action jumps directly to the node-level response without displaying the prompts associated with any of the remaining unfilled slots.
5. Click Back, and then click Save.
6. Now, you need to edit the node-level response to make it recognize when a user wants to exit the process rather than make a reservation. Add a conditional response for the node.

From the edit view of the node with slots, click Customize, click the Multiple responses toggle to turn it on, and then click Apply.

![Shows the Multiple responses toggle after it is turned on](https://cloud.ibm.com/docs-content/v1/content/a2b18c153837bce00a5b4de496e4b4ca64bbf56e/assistant-data/images/slots-multi-responses.png)
7. Scroll down to the response section for the node with slots, and then click Add response.
8. Add the following values to the fields.



Node-level conditional response details

 Condition Response 

 `has_skipped_slots` I look forward to helping you with your next reservation. Have a good day. 



The has_skipped_slots condition checks the properties of the slots node to see if any of the slots were skipped. The exit handler skips all remaining slots to go directly to the node response. So, when the has_skipped_slots property is present, you know the exit intent was triggered, and the dialog can display an alternate response.
Navigate back to the dashboard, and look for the new instance. Click on it to open the Activity Tracker console.

![Find AT](https://cloud.ibm.com/docs-content/v1/content/63322f2f3a72050206eb05ba7f590fdcb741105c/cloud-object-storage/images/at-tut-5-find-at.png)





 Step 6: Launch the Activity Tracker interface 

Now we can see some metadata about our new Activity Tracker instance (location, CRN, etc.). Click on the View IBM Cloud Activity Tracker* button to launch the interface.

![Open AT](https://cloud.ibm.com/docs-content/v1/content/63322f2f3a72050206eb05ba7f590fdcb741105c/cloud-object-storage/images/at-tut-6-open-at.png)

We'll quickly see that there's nothing here. It will take a little while for the new instance to be associated with the bucket - while data operations (like reading or writing objects) are immediately consistent, operations that update the bucket's metadata (such as adding an Activity Tracker association) are eventually consistent and may take 15 minutes or so to propagate across the system.

![View AT](https://cloud.ibm.com/docs-content/v1/content/63322f2f3a72050206eb05ba7f590fdcb741105c/cloud-object-storage/images/at-tut-7-empty-at.png)





 Step 7: Trigger an event 

Let's navigate back to our bucket. When we open the bucket in the console it will trigger a listing, even though the bucket is empty. Behind the scenes, the console is sending a GET bucket request to list the objects, and Activity Tracker is going to log this listing event.

!