Where to connect
- On the map: click the service, then Connect in its details. In the inventory, not connected opens the same details. Admins and owners also see Connect to confirm in the panel at the top of the map (open it with +): each service there that can be connected, with how many cloud resources connecting it would confirm.
- Not on the map yet (an account nothing in your code points to, like a cloud account managed by hand): next to choose repos, choose settings, then Connect another service…. If you add one and don’t connect it, Remove from map in its details takes it off again.
Two ways in
- A key. Every connector but Slack has one: the steps say how to make a key with the least access the vendor offers, read-only where it can be.
- Sign in with the service. One click, where Xerg offers it. Each connector’s page lists the exact scopes it asks for.
What Xerg does with it
- It only reads: lists, describes and counts. It never changes anything in your account.
- It never keeps your customers’ data: no database rows, emails, payments, messages or error events.
- The key or token is encrypted (AES-256-GCM), stored for your workspace only, and never sent back to a browser.