Skip to content
Learn
Presentations P-00000 to P-00999
Link a partner tenant to yours: the invitation, and what a connection is for

Link a partner tenant to yours: the invitation, and what a connection is for

Link a partner tenant to yours: map companies, branches and items · presentation 1 of 2 · for the whole-system operator — you run the books Read the transcript · Back to the series

These slides need JavaScript to advance one at a time. Without it every slide is shown below, one after another, each with its own player — or read the transcript, which carries the same steps and every word.

Link a partner tenant to yours: map companies, branches and items · presentation 1 of 2

Link a partner tenant to yours: the invitation, and what a connection is for

You can say when two businesses need a tenant-to-tenant link rather than a second company…

What a tenant link is for

Step 1 — Decide whether a link is what you need

You will know whether your situation calls for a tenant link at all.

What this step names
  1. The link lets the two agree which companies
  2. Branches and items correspond: the partner's companies and branches are readable across…
  3. Of your items the dealer sees only what you permit

Step 2 — Know what the link does, and what it will not do

You can say plainly what a connection buys you.

What this step names
  1. It lets one tenant
  2. The host
  3. Open a controlled slice to the other
  4. The guest: a company and branch pairing
  5. A list of items the guest may pair with its own
  6. A team of the partner's users

Connecting the two sides

Step 3 — Send the invitation from the host

The invitation exists on both sides.

Where this step sits
    flowchart TD
  s1["1. Decide whether a link is what…"]
  s2["2. Know what the link does…"]
  s3["3. Send the invitation from the host"]
  s4["4. Answer it from the guest…"]
  s5["5. Treat a connection as permanent"]
  s6["6. Give the right people the rights…"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5
  s5 --> s6
  classDef here fill:#1e40af,stroke:#1e40af,color:#ffffff,font-weight:bold;
  class s3 here;

Step 4 — Answer it from the guest, and read the four states

You can answer an invitation and read what a connection's status means.

What you do
  1. Reject makes both rejected

Step 5 — Treat a connection as permanent

You will not send a second invitation to a tenant that already has one.

Where this step sits
    flowchart TD
  s1["1. Decide whether a link is what…"]
  s2["2. Know what the link does…"]
  s3["3. Send the invitation from the host"]
  s4["4. Answer it from the guest…"]
  s5["5. Treat a connection as permanent"]
  s6["6. Give the right people the rights…"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5
  s5 --> s6
  classDef here fill:#1e40af,stroke:#1e40af,color:#ffffff,font-weight:bold;
  class s5 here;

Step 6 — Give the right people the rights, on both sides

You will know who can do what.

What this step names
  1. Every tenant-link action is open to the tenant's owner or administrator
  2. Otherwise needs one of its permission codes: separate families for invitations
  3. Company and branch mapping
  4. Item permission and pairing on each side
  5. External teams
  6. Roles

NarrationSlide 1 of 9

Left and right arrows, or the space bar, move between slides; f is full screen and Esc leaves it. Clicking the left or right half of a slide pages it. Play and pause belong to you — nothing moves on by itself unless you tick the box above.

Last updated on
Add a clock, rehearse it, and prove it fired — transcriptLink a partner tenant to yours: the invitation, and what a connection is for — transcript