> For the complete documentation index, see [llms.txt](https://developers.bloomcredit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.bloomcredit.io/docs/v2.1/enablement-services/mutations/registerorganizationusermutation.md).
# RegisterOrganizationUser
{% hint style="info" icon="lock" %}
**Authorization**
Requires Organization scoped authorization. See the [Enablement Services Authorization](/docs/v2.1/enablement-services/enablement-services-getting-started/enablement-services-authentication.md) guide.
{% endhint %}
The `registerOrganizationUser` mutation is used to create a new user in the database. Upon successful creation, the mutation will return the user's unique ID. You should store this ID in your database and associate it with your consumer record, as it will be required for accessing authenticated queries and mutations.
Below is an example of the `registerOrganizationUser` mutation, detailing all available input fields and the fields included in the output. The connections and tradelines fields in the output require additional inputs, as shown in the example.
{% code title="Mutation" %}
```graphql
mutation RegisterOrganizationUser {
registerOrganizationUser(
input: {
organizationSlug: String!
email: String!
phoneNumber: string!
name: NameInput!
address: AddressInput!
dateOfBirth: DateInput!
nationalId: String
visitorID: String
}
){
user {
id
email
phoneNumber
status
createdAt
updatedAt
syncedAt
closedAt
connection(input: ConnectionsInput!): ConnectionsConnection!
tradelines(input: TradelinesInput!): TradelinesConnection!
}
}
}
```
{% endcode %}
#### Input Attributes
| Attribute | Description |
| -------------------- | --------------------------------------------------------------------------- |
| **organizationSlug** | URL friendly name of organization |
| **email** | User's email address |
| **phoneNumber** | User's phone number |
| **name** | User's [name](/docs/v2.1/enablement-services/models/name.md) . |
| **address** | User's [address](/docs/v2.1/enablement-services/models/address.md) . |
| **dateOfBirth** | User's [date](/docs/v2.1/enablement-services/models/dateinput.md) of birth. |
| **nationalID** | User's SSN or TIN. (not required for Enablement Services) |
| **visitorID** | \[Description] |
***
#### Output Attributes - [User](/docs/v2.1/enablement-services/models/user.md)
| Attribute | Description |
| --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **id** | Global identifier for the user. |
| **email** | User's email address |
| **phoneNumber** | User's phone number |
| **name** | User's [name](/docs/v2.1/enablement-services/models/name.md). |
| **address** | User's [address](/docs/v2.1/enablement-services/models/address.md). |
| **status** | User's [status](/docs/v2.1/enablement-services/models/userstatus.md) |
| **notificationPreferences** | Notifications are currently not sent for Enablement Services |
| **legalAgreementVersions** | The Legal agreement versions the user has accepted. [LegalAgreementVersions](/docs/v2.1/enablement-services/models/legalagreementversions.md) |
| **createdAt** | The time the user was created in the database. |
| **updatedAt** | The last time the user was updated. |
| **syncedAt** | The last time this user's connections were synced. |
| **closedAt** | The time this user profile was closed. |
| | |
| **connections** | The financial institution connections the user has created. \* \*Requires the [ConnectionsInput](/docs/v2.1/enablement-services/models/connectionsinput.md) |
| **tradelines** | The tradelines associated with the connected financial institution(s) this user has connected. \*\*Requires the [TradelinesInput](/docs/v2.1/enablement-services/models/tradelinesinput.md) |
---
# 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://developers.bloomcredit.io/docs/v2.1/enablement-services/mutations/registerorganizationusermutation.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.