> For the complete documentation index, see [llms.txt](https://knowledge-base.letsgetdigital.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge-base.letsgetdigital.com/adding-users-and-ticketing/registration-forms/combined-user-and-company-registration.md).

# Combined User & Company Registration

It’s often useful to register a company at the same time as registering a user for an event. This allows exhibitors and sponsors to establish their presence without organisers having to collect and enter the data manually. By enabling this option, you let exhibitors set up their brand presence on their own terms while reducing admin work for your team.

<figure><img src="/files/5HaMVeqjP3tb5492opFQ" alt="A screenshot of a registration form showing Company-related questions. The fields are filled in with those of a fictional organisation. " width="563"><figcaption></figcaption></figure>

### Add company fields to a form

Companies are added in exactly the same way as the fields used for registering a user. To add a company, create a new form element and select the option  <mark style="background-color:$primary;">Company input</mark>. The first one will add the field <mark style="background-color:$primary;">Company name</mark>, which is essential for creating a company. To add more details, add another <mark style="background-color:$primary;">Company input</mark>. This time, the form element will contain new options to add different information about a company.&#x20;

<figure><img src="/files/pQIxi3LZoVOapb9wxDb0" alt="" width="563"><figcaption></figcaption></figure>

When registering a company, the user will be linked to the it and given the role <mark style="background-color:$primary;">Exhibitor Manager\*</mark>.&#x20;

Exhibitor managers have access to the <mark style="background-color:$primary;">Exhibitor Portal</mark>, where they can manage their company details further, select a booth on the Interactive Map, invite colleagues to the Company, and more.&#x20;

{% hint style="info" %}
For more information about the Exhibitor Portal, see [Exhibitor Portal](/event-contributor-portals/exhibitor-portal.md)
{% endhint %}

\*If the Exhibitor portal is not active, the role <mark style="background-color:$primary;">Exhibitor</mark> is given instead.&#x20;

***

### Hidden companies

When a company is created through the Registration form, it is hidden by default on the Let’s Get Digital platform. This gives exhibitors time to complete their profiles before becoming visible to potential leads.

<figure><img src="/files/xDBtRLCcbYWkYDVzO4iX" alt="" width="563"><figcaption></figcaption></figure>

Event organisers can make a company visible once its profile meets the required standard for the Virtual Event/App.

<figure><img src="/files/irPMKyXGJIbl6YHYovgl" alt="" width="563"><figcaption></figcaption></figure>

Hidden companies can be located by filtering for the “Hidden” tag in the Company overview within the Admin Panel.&#x20;

The option to show/hide a company will only become visible after a company has been made with the Registration Form.&#x20;

***

### Company Tags

When setting up Registration forms, assign tags to distinguish between company types (e.g. exhibitor ticket tiers). These tags will automatically be applied when a company is created, allowing you to filter and manage them more easily in the Admin Panel.

<figure><img src="/files/KzxnBNf8X9reBPMmvzv0" alt="" width="563"><figcaption></figcaption></figure>

Assign company tags in the Settings tab of the Registration Form editor. You can add one or more tags, which will be automatically applied when the form is submitted.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://knowledge-base.letsgetdigital.com/adding-users-and-ticketing/registration-forms/combined-user-and-company-registration.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
