> ## Documentation Index
> Fetch the complete documentation index at: https://docs.go.gbgplc.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> Manage resources on behalf of your sub-organisations from a single place, and share journeys automatically without duplicating them.

A partner account lets you manage resources on behalf of your sub-organisations from a single place.

As a partner, you own and manage resources, such as journeys, flows, and deliveries. You can share the journeys you own with your sub-organisations automatically, without duplicating the underlying resources. For the underlying concepts, see [Partner organisations](/docs/go-v1/get-started/key-concepts#partner-organisations).

You log in with your partner account the same way as any other user. For the steps, see [Log in to GBG GO](/docs/go-v1/platform/journey-builder/access-gbg-go).

<Note>All sub-organisations are created by GBG.</Note>

## What you can do

You use the same journey-building tools as a customer, then share the resulting journeys with your sub-organisations. As a partner, you can:

* [Create a journey](/docs/go-v1/platform/journey-builder/create-journey) for your sub-organisations to use.
* [Configure modules](/docs/go-v1/platform/journey-builder/configure-module) to add verification checks to a journey.
* [Set up routing](/docs/go-v1/platform/journey-builder/set-up-routing) to control how a journey branches.
* [Set up evaluation](/docs/go-v1/platform/journey-builder/set-up-evaluation) to define outcome and decision logic.
* [Publish a journey](/docs/go-v1/platform/journey-builder/publish-journey) to make it available to your sub-organisations.

## How sharing works

When you share a journey, your sub-organisations receive a reference to it rather than a copy. Sub-organisations don't own a duplicate of the underlying resource.

Sharing has the following characteristics:

* Updates apply automatically. When you update a journey, all sub-organisations use the updated version. There is no manual propagation step.
* Journey IDs stay the same. You use the same journey resource ID in the partner organisation and in each sub-organisation.
* Sharing is one-directional. Resources always flow from the partner down to sub-organisations. Sub-organisations can't push resources up.

### When you update a journey

When you modify and republish a journey, the update applies as follows:

* The updated version applies to all sub-organisations. The sub-organisation does not need to take any action.
* New sessions that reference a specific version use that version, not the update. To run the updated journey, start the session against the new version.
* New sessions that reference the journey as `@latest` use the updated version. Use `@latest` when you want updates to reach sub-organisations without changing your integration. Name a specific version when you need to control exactly which version each session runs.
* In-flight sessions continue with the version they started on.

## What gets shared

The partner organisation manages shared resources centrally. Each sub-organisation manages its own account-level resources.

| Shared from partner to sub-organisations | Managed by each organisation                |
| ---------------------------------------- | ------------------------------------------- |
| Journeys                                 | Licences                                    |
| Flows                                    | Credentials, such as API keys and passwords |
| Deliveries                               | Users and roles                             |
|                                          | Departments                                 |
|                                          | Data retention policies                     |
|                                          | Organisation settings                       |

Users and roles apply to people who sign in to the **GBG GO platform** directly. Each organisation creates its own users and assigns their roles. [Single URL Login](/docs/go-v1/platform/partner-login/single-url-login) works differently: you request the role or permissions for each session, and the session never holds more than your own credentials hold.