> For the complete documentation index, see [llms.txt](https://docs.korewireless.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.korewireless.com/kore/iam/accounts.md).
# Accounts
What is a KORE Account?
A KORE account is the fundamental part of accessing any KORE offering. When you first register with KORE, you will create your first account as part of the registration process. This account grants you access to KORE's various offerings, which you can immediately utilize upon registration or by contacting KORE for access.
Your account(s) are managed centrally across KORE through the KORE Console. You can view your account details by logging into the KORE Console and navigating to your [account details](https://console.korewireless.com/accounts).
## Account Types
There are two types of accounts, which you would have chosen at the time of registration for your first account:
1. Individual Account
2. Business Account
You can see your account type by navigating to the [KORE console](https://console.korewireless.com) and then to account details:
### **Individual Accounts**
This is typically selected if you are not a business or are interested in one or more of KORE's offerings and wish to experiment, build a proof of concept, or tinker away with our APIs. An individual account type gives you access to features and functions similar to those of a business account.
### **Business Accounts**
This account type is selected if you are a business which requires additional information for KORE to invoice and do business with you correctly.
{% hint style="info" %}
It is best practice for business accounts to enter details that relate to the business rather than personal information.
{% endhint %}
## Editing Account Details
{% hint style="info" %}
Users cannot change all the details of an account, like the account name and email address.
Contact support for properties you wish to change but cannot.
{% endhint %}
You can edit your account by heading to the [account details](https://console.korewireless.com/accounts) page and editing the details.
The account details that can be edited are
* Company phone number (including country code)
* Country / Region
* Street address
* Apt, Suite, etc. (optional)
* City
* VAT / Company Tax ID
* State / Province
* Street / P.O Box
## Account Status
Regardless of the type, your account can have one of the following statuses.
1. **Pending -** The temporary state before an account is activated.
2. **Active** - The initial state of the account.
3. **Suspended** - Your account is still active but unable to be used due to things like unpaid bills. Contact Support for more information.
4. **Deactivated** - The final state of the account after explicit action to close or deactivate. You are unable to reaccess the account.
### Pending Account Status
If you are registering as a [business ](/kore/iam/accounts.md#business-accounts)and are based in the European Union, your account will stay in a Pending state until KORE can verify your VAT number, that happens in near real time. If your account is stuck in a pending state, refer to our [guide ](/kore/iam/how-to/resolve-account-in-a-pending-state.md)to troubleshoot.
### Account Status Flow
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.korewireless.com/kore/iam/accounts.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
.png?alt=media&token=7190f7ae-2cf5-483d-a133-7b9d40e98cc0){kind=spacer}