Sharing devices with another organization (associated organizations)

Last updated: October 15, 2026

Associated organizations let two organizations on Texture share devices with each other, for example a utility monitoring, and later dispatching, batteries managed by an aggregator. Both organizations agree to the association, each decides what it shares, and either one can end it at any time.

Key ideas

  • Associations are agreed by both sides. Nothing is shared until an administrator in each organization takes part, and either side can end the association.

  • You only ever share your own devices. A grant is your organization's decision about your own resources. It's shared from one of your workspaces and lands in a workspace the other organization chooses.

  • Two levels of access: Monitor (view) and Control (view and send commands). Control includes Monitor.

  • Sharing with an organization isn't sharing with everyone in it. The receiving organization's own roles and team permissions still decide which of its people can see or control shared devices.

  • Changes take effect right away. Nothing is copied between organizations, so when a grant is added or removed, the next view reflects it.

Grants describe a set of devices, not a list

A grant names the access level, the kind of resource (devices today), and conditions on the devices, such as state is OR or manufacturer is Tesla. Because it's a set of conditions rather than a fixed list, it also covers devices added later that match.

Requesting access from another organization

  1. Go to Settings > Organization and find Associated organizations.

  2. Select Invite an organization and enter an email address at the other organization. The association is between the two organizations, and any administrator there can respond.

  3. To ask for access, select Request access and describe what you need: the kind of resource, Monitor or Control, the conditions (for example State is OR), and which of your workspaces it should appear in.

  4. Send the invitation. You'll see it as pending, and you can withdraw it until the other side responds.

A request is only a request: you won't see anything of theirs until they grant it.

Responding to a request

When another organization asks for access, your administrators see a notice and a request card in Settings > Organization, with Review & accept and Decline.

Review & accept opens the request pre-filled, and everything in it is yours to change. You can narrow or widen the conditions, change the access level, choose which of your workspaces it's shared from, add a grant they didn't ask for, or accept the association without granting anything.

Before you grant anything, Preview in Explore shows exactly which devices the grant would reach.

If you accept a request exactly as asked, it appears straight away in the workspace the requester chose. If you change it, the other organization chooses where it lands.

Offering access without being asked

You can also grant access to your own devices without a request, either when you send an invitation or later on an existing association. The other organization's administrators are notified and choose which of their workspaces it lands in. Each side keeps control: you decide what leaves, they decide where it arrives.

What people in the receiving organization see

Shared devices appear in Explore alongside your own, with the Organization column naming the organization they came from, so a shared device is never mistaken for one you own.

What each person can do depends on both layers:

  • The grant sets the most access anyone in the receiving organization can have. If a grant is Monitor, nobody can send commands, even administrators.

  • Within that, the receiving organization's roles and team permissions decide who sees and controls what. For example, a team limited to Tesla devices only sees the shared devices that are also Tesla.

So when a partner opens Control, administrators get it right away, and the receiving organization then decides which teams get it too.

Roles and access in your organization

  • Admin: control over your organization's resources, and can administer the organization, including associations.

  • Operator: control over your organization's resources.

  • Viewer and User: view your organization's resources; team permissions can give them control over specific devices.

  • Scoped: access only through team permissions.

Seeing what a partner did with your devices

Commands sent by an associated organization show on the device's command history and on your workspace's Commands page, with Dispatched by naming the organization that sent them.

Changing or ending an association

Either side can manage a live association at any time: grant more access, request more, review and revoke grants you've made, and move grants you've received to a different workspace.

  • Revoking a grant removes only that grant. Other grants stay, so you can take back Control while Monitor continues.

  • Ending the association removes every grant in both directions at once.

Either way, the change applies on the other side's next view, and nothing needs cleaning up because nothing was copied.

Good to know

  • Associating shares your organization's domain name with the other organization.

  • Devices are the kind of resource that can be shared today.

  • Each grant lands in one workspace in the receiving organization.