# Members

The user who first registers an Organisation on OnePub is nominated as the owner/administrator.

The owner can invite additional members to their Organisation via the 'Invite' button on the home page.

![](/files/14dpvpcYAcpogI2ysjpA) 

{% tabs %}
{% tab title="Free" %}
The free edition allows two members per Organisation.
{% endtab %}

{% tab title="Pro" %}
Only the original owner can invite other team members.
{% endtab %}

{% tab title="Team" %}
Only the Team owner can invite members to their team.

Only the Organisation owner can create teams.
{% endtab %}

{% tab title="Enterprise" %}
Specify multiple Team owners and multiple Publisher owners to manage teams.
{% endtab %}
{% endtabs %}

You can use a single email address across multiple OnePub Organisations and [switch between organisations](/workflows/switching-organisations.md) via the OnePub profile and the OnePub CLI tooling.

Once a user has become a member they can publish new packages and add a private package as a dependency to their project (subject to permissions).

The user who first publishes a package is considered the owner of that package.

{% tabs %}
{% tab title="Pro" %}
Any member can publish a package and upload a new version to any existing package.
{% endtab %}

{% tab title="Team" %}
Only a Team leader can publish a package or update a published version.
{% endtab %}

{% tab title="Enterprise" %}
Designate multiple package owners who can update existing packages.
{% endtab %}
{% endtabs %}


---

# Agent Instructions: 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:

```
GET https://docs.onepub.dev/fundamentals/members.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.