customer can become an officehub and then

• add sub-accounts (fully fledged customers)
• impersonate them (act on their behalf, see their contracts...)

• subaccounts are regular customers
• they need to be finished by someone from the company they represent
• officehub gets all notifications unless sub-account is finished

• customer app + marketplace
• vendor app

• API

  • /me

  • /public/subaccount/{sub-account}

  • /customer/officehub/*

• HUB
  • email interception
  • email for finishing sub-account

• any customer can toggle on (FF!)
• new menu items
  • subaccounts
  • tasks
  • lunch overview

• authed users from an officehub get access to /customer/officehub namespace

• token exchange via /customer/officehub/login-as

• token exchange via /customer/officehub/logout

• new token is placed and app is refreshed

act on behalf of their sub-account(s)

• N.b. still same user, just temp attached to other customer

• email is sent as soon as sub-account is created by OH

• as long as sub-account is not finished, all emails are re-routed to the officehub

• click go to app and check invite status via `/public/sub-account/ endpoint`

• invitation link sent to sub-account owner contains sub-account identifier

• e.g. sub-account_42_sub-account

• invite un-used:

• user is routed into the setup

• logged into app when finished

• if invite already used: user is routed into the app (or login)