vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Managing accounts and users (ibmcloud account) 

Use the following commands from the IBM Cloud® Command Line Interface to manage accounts and users in an account.



 ibmcloud account orgs 

List all organizations:

ibmcloud account orgs [-r REGION_NAME] [--guid] [-c ACCOUNT_ID] [-u ACCOUNT_OWNER]



 Command options 

-r REGION_NAME
: Region name. List the organizations in the region specified. Default to current region if not specified. If set to 'all', list the organizations in all regions.

--guid
: Display the guid of the organizations. This option is exclusive with --output.

-c ACCOUNT_ID
: Account ID. List the organizations under the account. Default to current account if not specified. If set to all, list organizations under all accounts. This option is exclusive with -u.

-u ACCOUNT_OWNER
: Account owner name. List the organizations under the accounts that are owned by the user. Default to current account if not specified. If set to 'all', list organizations under all accounts. This option is exclusive with -c.





 Examples 

List all the organizations in region us-south with the GUID displayed:

ibmcloud account orgs -r us-south --guid

List all the organizations in JSON format:

ibmcloud account orgs --output JSON







 ibmcloud account org 

Show the information of the specified organization:

ibmcloud account org ORG_NAME [-r REGION] [--guid]



 Command options 

ORG_NAME (required)
: The name of the organization.

-r REGION
: Region name. If not specified, the default is current region. If set to all, orgs with the given name in all regions are listed.

--guid
: Retrieve and display the org's guid. All other output for the org is suppressed. This option is exclusive with --output.





 Examples 

Show the information of organization IBM with the GUID displayed:
These options include the use of time-based one-time passcode authentication, security questions, third-party authentication mechanisms, and password expiration rules. For more information, see [Types of multifactor authentication](https://cloud.ibm.com/docs/account?topic=account-types).

You can regularly review the list of account users and remove users who don't need access to the account. For more information, see [Removing users from an account](https://cloud.ibm.com/docs/account?topic=account-remove).
* Why can't I see my emissions data?

You might not be able to view your accounts emissions data because you don't have the right access or the service doesn't have enough data. For access, account owners, account administrators, and users with a viewer role or higher on the billing service can view and export emissions data for the entire account. Supported services must have at least 30 days of data to be viewed on the carbon calculator.

If you're still having issues viewing data, [create a support case](https://cloud.ibm.com/unifiedsupport/cases/form) in the IBM Cloud Support Center.
* How do you calculate the emissions?

The total emissions are calculated by comparing the energy-related usage with data center energy sources. Emissions from key greenhouse gases are measured in metric tons of carbon dioxide-equivalent (kgCO2e). You can download the total emissions data in CSV format. View the total emissions widget on the [Carbon Calculator](https://cloud.ibm.com/billing/carbon-calculator) page in the console.
* Can I view emissions for all services on my account?

Emissions data is currently tracked for a subset of services, but more services are under consideration to be added. Emission data is currently available for the following services:



* Bare Metal Servers for Classic
* Bare Metal Servers for VPC
* Cloud HSM
* Cloud Object Storage
* FortiGate Security Appliance 10Gbps
* Kubernetes Service
* Load Balancers for Classic
* Virtual Server for Classic
* Virtual Server for VPC
Who do I reach out for support? 



1. Open any issues directly with RackWare support team. The support team is available 365x24x7.
2. Open a case by using the following options:

a. Email: [support@rackwareinc.com](mailto:support@rackwareinc.com)

b. Phone: +1 (844) 797-8776

c. In all cases, add 'RackWare RMM - IBM Cloud’ in the subject line. The RackWare support is based in the United States and India.







 Is data migration supported for File or Block performance endurance storage? 

Only local storage and Block performance endurance storage is supported in IBM Cloud classic. File performance and endurance volume’s data migration is not supported; for this, consider using a third-party tool such as rsync. A sample script using rsync can be found [here](https://github.com/IBM-Cloud/vpc-migration-tools).
They can't be moved to a different enterprise or removed from the enterprise to be a stand-alone account.

To move an account, you need the Administrator role on the Billing service in the enterprise account and the Editor or Administrator role on either the entire enterprise or both the current and target account groups.



 Moving an account in the console 



1. From the Enterprise dashboard in the console, click Accounts.
2. In the Accounts section, click the Actions icon ![Actions icon](https://cloud.ibm.com/docs-content/v1/content/d4595e5202a9a27767cf034e81b038cdf772e0d5/icons/actions-icon-vertical.svg) in the row for the account, and select Move account.
3. Select the new parent for the account, and click Save.







 Moving an account by using the CLI 



1. Find the account name and ID by listing all accounts in your enterprise.

ibmcloud enterprise accounts --recursive
2. If you're moving the account to an account group, find the account group name and ID.

ibmcloud enterprise account-groups
3. Move the account by specifying the new parent on the related option.

To move the account to an account group, specify the account group name on the --parent-account-group option.

ibmcloud enterprise account-move -n NAME --parent-account-group ACCOUNT_GROUP_NAME

To move the account directly under the enterprise, specify the --parent-enterprise option.

ibmcloud enterprise account-move -n NAME --parent-enterprise







 Moving accounts by using the API 

You can move an account by calling the Enterprise Management API as shown in the following sample request. Replace the IAM token and ID variables with the values from your enterprise.



* Curl
* Java
* Python
* Go
* Node



curl -X PATCH "https://enterprise.cloud.ibm.com/v1/accounts/$ACCOUNT_ID"
-H "Authorization: Bearer <IAM_Token>"
* The enterprise account is always a direct child of the enterprise and can't be moved, so you won't have the flexibility to change how usage is reported for the resources.
* The enterprise account contains the users and access for managing the enterprise and its billing, so only users with those responsibilities should be added to the account.



Users within each account in the enterprise can create, use, and collaborate on resources just as you can in a stand-alone account. For details, see [Managing resources](https://cloud.ibm.com/docs/account?topic=account-manage_resource). Enterprise users can't directly work with resources within child accounts, but they can monitor the resource types and plans that are used in each account by viewing their usage. For more information, see [Viewing usage in an enterprise](https://cloud.ibm.com/docs/billing-usage?topic=billing-usage-enterprise-usage).
Migrating pre-V2.5 vCenter Server with Hybridity Bundle instances to IBM Cloud accounts 

VMware vCenter Server® with Hybridity Bundle instances that are deployed in V2.5 and later in your IBM Cloud® account are automatically added to your account. These instances are managed by IBM Cloud Identity and Access Management (IAM).

For instances that were deployed in V2.4 and early releases, you can migrate them to specified IBM Cloud accounts for IAM-enabled user management.



 Before you begin 

Ensure that the IBM Cloud account that you want to migrate the instance to is not an IaaS-only account. An IaaS-only account is an IBM Cloud infrastructure account that is not linked to an IBM Cloud account.

For more information about how to link your Iaas-only account to your PaaS account, see [Follow these steps to link your IaaS and PaaS accounts](https://www.ibm.com/cloud/blog/follow-steps-link-iaas-paas-accounts).





 Procedure to migrate instances 



1. In the IBM Cloud for VMware Solutions console, click Resources > vCenter Server from the left navigation pane.
2. From the console banner, click your user account icon, and then click the Account field to select the user account that you want to migrate the instance to.
3. In the vCenter Server table, find the pre-V2.5 instance.
4. In the Actions column, click the vertical overflow menu icon, 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 > vCenter Server 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)
* An account administrator can grant specific users access to Cloud Shell and its features, even if Cloud Shell settings are disabled at the account level. For more information, see [Assigning access to Cloud Shell and its features at a user level](https://cloud.ibm.com/docs/account?topic=account-shell-settingsshell-access-user).
* The following new service roles are available:



* Cloud Operator
* Cloud Developer
* File Manager



For more information, see [IAM roles and actions](https://cloud.ibm.com/docs/account?topic=account-iam-service-roles-actionsibm-cloud-shell).
* IBM Cloud Shell now uses a Red Hat™ Linux™ bash shell instead of a x86-64 Ubuntu Linux™ bash shell.







 18 September 2020 



* Account owners or users with Cloud Shell administrator access can manage Cloud Shell settings from the IBM Cloud console. For more information, see the following topics:



* [Updating Cloud Shell settings](https://cloud.ibm.com/docs/account?topic=account-shell-settings)
* [Actions and roles for account management services](https://cloud.ibm.com/docs/account?topic=account-account-servicesshell-service-account-management)



* The following tools are new with this Cloud Shell update:



* Terraform version switch (tfswitch) version 0.8.832
* Tekton CLI (tkn) version 0.12.0



* The following tools are updated with this Cloud Shell update:



* kn upgrade to 0.14.0
* The IBM Cloud CLI (ibmcloud) is upgraded to version 1.2.1, and the CLI plug-ins are upgraded to the most recent versions









 12 August 2020 



* Increased the weekly usage quota from 30 hours to 50 hours so you have more time to use Cloud Shell each week. For more information about the usage quota, see [Tracking your usage](https://cloud.ibm.com/docs/cloud-shell?topic=cloud-shell-shell-uiusage-limit).
curl --location --request POST 'https://iam.cloud.ibm.com/v1/policies' --header 'Content-Type: application/json' --header 'Authorization: <your token>' --data-raw '{
"description": "useful description here",
"type": "access",
"subjects": [
{
"attributes":
{
"name": "iam_id",
"value": "<user iam-id>"
}
]
}
],
"roles": [
{
"role_id": "crn:v1:bluemix:public:is::::serviceRole:VPNClient"
}
],
"resources": [
{
"attributes":
{
"name": "serviceName",
"value": "is",
"operator": "stringEquals"
},
{
"name": "accountId",
"value": "<your account id>"
}
],
"tags":
{
"name": "abc",
"value": "test"
}
]
}
]
}'





 Using CLI for Assigning Service Defined roles 

Assigning Service Defined roles to an access policy with an access management tag by using the UI isn't supported. This feature is supported only through the API and CLI. Use the following example for CLI.

ic iam access-group-policy-create Developers_MyApp --roles Viewer --service-name kms --tags abc:test







 Related links 

For more information about IAM, resource groups, access groups, and access management tags, see the following IBM Cloud topics:



* [IBM Cloud IAM](https://cloud.ibm.com/docs/account?topic=account-iamoverview)
Enabling HIPAA support for your account 

If you're the account owner, you can enable your IBM Cloud® account to be HIPAA supported. HIPAA support can be useful if you plan to include Protected Health Information (PHI) in HIPAA-enabled services.

The US Health Insurance Portability and Accountability Act (HIPAA) and the Health Information Technology for Economic and Clinical Health (HITECH) Act define standards for handling electronic healthcare transactions and information. If you or your company is a covered entity as defined by HIPAA, you must enable the HIPAA Supported setting if you run sensitive workloads that are regulated under HIPAA and the HITECH Act. Learn more about IBM Cloud compliance in [Compliance on the IBM Cloud](https://www.ibm.com/cloud/compliance).

Enabling this setting has the following effects:



* Enables you to filter on HIPAA Enabled services in the catalog
* Indicates to IBM that your account stores protected health information (PHI)
* Digitally accepts the IBM Business Associate Addendum (BAA) for covered entities



Enable this setting only if you or your company is a covered entity as defined by HIPAA. If you or your company is a business associate of a covered entity, [contact IBM Cloud Sales](https://www.ibm.com/account/reg/us-en/signup?formid=MAIL-wcp) to accept the applicable BAA. For more information about HIPAA definitions of covered entities and business associates, see the [US Department of Health & Human Services](https://www.hhs.gov/hipaa/for-professionals/covered-entities/index.html) website.

Accounts that enable the HIPAA Supported setting still have access to the full catalog of services. IBM Cloud services typically offer multiple plans. The HIPAA Enabled label on a service can apply to all available plans or be limited to specific plans or configurations. You as the client are solely responsible for limiting PHI to HIPAA Enabled product plans and architecting in accordance with HIPAA and HITECH.



1. In the IBM Cloud console, go to Manage > Account, and select Account setting in the console.
2. For the HIPAA Supported option, click On.
3. Read the information about enabling this setting.
For more information, contact [IBM Sales](https://www.ibm.com/contact/us/en/).





 Where can I find help for a problem that I'm having? 

For information about posting questions on a forum or opening a support ticket, see:



* [Opening tickets](https://cloud.ibm.com/docs/netezza?topic=netezza-tickets&interface=ui)
* [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter)
* [IBM Cloud® support forum](https://www.ibm.com/mysupport/s/forumshome?language=en_US)
* [IBM Hybrid Data Management Community](https://community.ibm.com/community/user/hybriddatamanagement/home)
Also make sure you have [appropriate access](https://cloud.ibm.com/docs/account?topic=account-iamfaqiam-access). If the error occurs again, follow the [troubleshooting steps for console pages that don’t load](https://cloud.ibm.com/docs/account?topic=account-ts_err). If the problem continues, go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI0305E 

Message: The usage information could not be displayed.

If you see this message again, go to the [IBM Cloud status page](https://cloud.ibm.com/status?selected=status) to check whether a service or component has an issue. Also make sure you have [appropriate access](https://cloud.ibm.com/docs/account?topic=account-iamfaqiam-access). If the error occurs again, follow the [troubleshooting steps for console pages that don’t load](https://cloud.ibm.com/docs/account?topic=account-ts_err). If the problem continues, go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI0306E 

Message: Third-party services information could not be retrieved.

Try again later. If you see this message again, go to the [IBM Cloud status page](https://cloud.ibm.com/status?selected=status) to check whether a service or component has an issue. If the problem continues, go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI0307E 

Message: Promotional codes can't be applied at this time.

Try again later. If you see this message again, go to the [IBM Cloud status page](https://cloud.ibm.com/status?selected=status) to check whether a service or component has an issue.
Which is the right federation option for you? 

In the past, IBM Cloud supported integration with customer's user directories by using IBMid SAML federation. In May 2020, IBM Cloud introduced an alternative method for clients to federate identities with their IBM Cloud account.

By default, when you create an account in IBM Cloud you use an IBMid for user identity. IBMid is the ID as a Service (IDaaS) from IBM used to access IBM web-based services, including IBM Cloud resources. The IBMid is based on your company's email address and a password that is managed by IBMid. IBMid allows you to federate to your own corporate user directory or a third-party Identity Provider (IdP) service that you might already use, such as Okta.

Federating to your own directory simplifies the process of adding users to your account, without requiring an IBMid with a separate password. However, there are cases where it might not be feasible for you to use IBMid to federate your corporate user directory. The alternative is to create an IBM Cloud App ID instance in your account and connect it to your chosen IdP.

This topic explains the differences between the following two methods:



* Federating with IBMid.
* Federating with your own instance of IBM Cloud App ID.



To decide which option is applicable to your use case, review the following sections.



 Which SAML federation options exist in IBM Cloud? 

IBM Cloud supports the following user types:

Non-federated IBMid users
: Users with a valid email address can create an IBMid and let IBMid manage the password. Your company email domain is not federated with IBMid, and you choose to keep it as is. Any user that uses your email domain can create their own IBMid, and the password they create is managed by IBMid. They can create an IBM Cloud account and invite other users with an IBMid to their account. They can also access other IBM web offerings by using that same IBMid.

Federated IBMid users
: Enterprise customers often connect their internal user directory, or IdP, with IBMid so that their employees don't need to manage an additional password.
Enabling your account to use Financial Services Validated products 

If you're the account owner, you can enable your IBM Cloud® account to be Financial Services Validated designated, which means your account stores and manages regulated financial services information.

Services that are designated as [IBM Cloud for Financial Services Validated](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-about) leverage the industry’s highest levels of encryption certification, provides preventive and compensatory controls for financial services regulatory workloads, multi-architecture support and proactive, and automated security.

The IBM Cloud for Financial Services Validated designation is available for services that are operating in select

multizone regions. Go to the [IBM Cloud Framework for Financial Services documentation](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-best-practicesbest-practices-financial-services-regions) for a list of supported multizone regions.

Accounts that enable the Financial Services Validated setting can filter the catalog to view the services that adhere to this compliance standard and still have access to the full catalog of services. However, if anyone in the account chooses to create a service that isn't Financial Services Validated, a message displays with a reminder that this setting is enabled in the account and the selected service isn't Financial Services Validated.

When you enable this setting, you are indicating that your account stores regulated Financial Services information.



1.  In the IBM Cloud console, go to Manage > Account, and select Account settings.
2.  For the Financial Services Validated option, click On.
3.  Read the information about enabling the setting, and select I understand and agree to these terms.
4.  Click On.



After you enable the setting at the account level, you can filter the IBM Cloud catalog to display services that are designated as Financial Services Validated. In the IBM Cloud catalog, expand the Compliance section and select Financial Services Validated. The Financial Services Validated label on a service can apply to all available plans or be limited to specific plans or configurations.
Or, about resource-related items, such as incidents, maintenance, security bulletins and resource activity. Additionally, if you have a Pay-As-You-Go or Subscription account, you can choose whether to receive IBM Cloud infrastructure service updates about changes, such as OS reloads, assigned IPs, and image and firmware updates. For more information, see [Setting email preferences for notifications](https://cloud.ibm.com/docs/account?topic=account-email-prefs).

You cannot set email preferences for receiving account type notifications. On the IBM Cloud [Notifications page](https://cloud.ibm.com/notifications), you can use the search field to locate an invitation or filter by the notification type called account.

Users already present in IBM Cloud receives an email and a notification with an invitation link. If an email address does not correspond to a known user in IBM Cloud, an invitation email gets sent to accept, but users can also choose not to accept the invitation. For more information, see [Setting email preferences for notifications](https://cloud.ibm.com/docs/account?topic=account-email-prefs) and [Inviting users to an account](https://cloud.ibm.com/docs/account?topic=account-iamuserinv).

The invitations expire after 30 days. New users to IBM Cloud can only accept an invitation by using the invitation link that they received through email.





 Checking the delivery status of email notifications and viewing email history 

On the [Communication history page](https://cloud.ibm.com/messaging), you can check the status of all email notifications that are sent to you, and you can verify whether the emails are delivered successfully. You can also view the last 90 days of IBM Cloud email history, which can help you save time by troubleshooting any delivery issues without you having to contact IBM support.

To view your email notification history and check the delivery status of an IBM Cloud email, complete the following steps:



1. In the IBM Cloud console, click the Notifications icon !