Skip to main content

What apps receive

For each user on each contact, Rollout signs a context, with the app’s publisher’s secret, that holds:
  • the user: your sub as user.id, and the embed.user name and email;
  • their account and org: your embed.account and embed.org;
  • the contact: your id for it as crm.personId, and the embed.person name and stage when they describe that contact;
  • where it came from: your marketplace’s id, your CRM’s key, the app’s id, and an expiry five minutes away.
That’s all. The context comes only from the claims in the token you sign, so you decide what each app can know.

What apps never receive

  • The contact’s emails and phone numbers. Rollout drops them from your claims even if you send them.
  • Your token. Apps get a context signed for them, never the token your server signed.
  • Anything from your page. Apps can’t read your page, its storage or its cookies.
A publisher that also uses Rollout’s Universal API may receive the contact’s Universal API id, when the user has connected their own CRM account to that publisher. The full shape of the context is in the context fields reference.

Apps are kept out of your page

  • Two frames deep. Your page loads the Rollout frame from Rollout’s origin, and each app loads in its own frame inside it. Apps never run in your page, and the signed contexts and the apps’ traffic stay inside the Rollout frame, out of reach of your page’s scripts.
  • Sandboxed. Each app frame is sandboxed with allow-scripts allow-same-origin allow-forms allow-popups allow-popups-to-escape-sandbox. An app can’t navigate your page or show dialogs over it.
  • Only approved origins. The Rollout frame lets app frames load only the origins of your marketplace’s approved apps, and accepts each app’s messages only from its own origin.
  • Only your pages. Rollout renders only inside the pages you list under Pages that may show the apps. Browsers refuse it anywhere else.
  • Nothing from publishers’ servers. Your page loads the library, the frame and the app icons from Rollout’s origin only.

Your user tokens

  • Signed on your server, with your client secret, for the user signed in to your CRM. Check that the user may see a contact before you sign a token for it.
  • Short-lived. A token can last at most an hour. Ten minutes is plenty: the components ask for a fresh one when they need it.
  • Good for one thing. A token with an embed:* scope works only for the embedded apps. Rollout’s Universal API refuses it, so a script on your page can’t use it to read or connect anyone’s accounts.
  • Scoped. embed:render only shows apps. Turning apps on needs embed:enable, and turning them on for an org needs embed:enable_org, which you give your org admins only.

You stay in control

  • Nothing reaches your users until you approve it.
  • An approval covers the URL you reviewed. If a publisher changes its app’s URL, the app is hidden until you approve it again.
  • You can suspend an app at any time, which hides it from every user at once.