Connect services and your own bucket
Connect a service once in Orbit and every satellite uses it. Keep your organisation's uploaded files and nightly backups in your own S3-compatible bucket, pick files from Cloudinary, Bynder or Frontify, post notices to Slack or Microsoft Teams, deploy on Vercel or Netlify, and connect Shopify, translation services and Algolia.
How-to guide11 min read
Connections is where your organisation connects the services it already uses, such as its own storage. You connect each service once, and every satellite that has a use for it works with it. There is nothing to install and nothing to switch on in each satellite.
Owners and admins open it from Organisations: choose your organisation, then Connections.
What you can connect
Services are grouped by what they do. Each one shows its status, which satellites use it, and where the service keeps your data.
Every service on this page is ready to connect today.
The status next to each service is one of:
- Not connected: nothing is set up yet.
- Active: the last check passed and the satellites use it.
- Failing: the last check, or the last file the satellites tried to save, didn't work. The row says what went wrong. Fix it, then choose Test.
Plans
Your own bucket is on every plan, Starter included. The other services need Growth or higher. Plans are per satellite, so you can connect one of them when at least one of your satellites is on Growth or higher, and each satellite uses it while that satellite is on Growth or higher. On Starter the buttons stay visible and say Growth and up. See Plans and billing.
Connect your own bucket
Every file people upload in any satellite, such as images in CMS Orbit's media library, trip photos in Travel Orbit, product images in Commerce Orbit or CVs in Careers Orbit, can be kept in a bucket your organisation owns. Any S3-compatible storage works: AWS S3, Cloudflare R2, IONOS, Hetzner, Wasabi and others.
- Create a bucket with your storage provider, such as
northwilds-media. It can stay private. - Create an access key that may write, read, list and delete files in that bucket, and nothing else.
- In Orbit, choose Connect next to Your own bucket.
- Fill in:
- Address: the https address of the storage service, such as
https://s3.eu-central-1.amazonaws.comfor AWS in Frankfurt, or the account address Cloudflare R2 shows you. - Region: such as
eu-central-1. For Cloudflare R2, useauto. - Bucket: the bucket's name.
- Folder (optional): a folder in the bucket to keep everything under, such as
orbit. - Access key and Secret: from step 2.
- Address: the https address of the storage service, such as
- Choose Test and connect.
Orbit writes a small test file to the bucket, reads it back and deletes it. Only when that works is the connection saved. If it doesn't, Orbit says what went wrong, for example that the bucket refused the keys or that there is no bucket with that name.
Addresses on private or internal networks are refused, and so are plain http:// addresses.
What happens to your files
From then on, new uploads in every satellite go to your bucket. Inside it, each satellite has its own folder: cms/, travel/, commerce/, booking/, careers/ and presence/.
Files keep the same addresses they would have had in Orbit. They are still served through Bifröst Orbit and its image cache, which also makes the smaller sizes and modern formats for images. Your websites and emails don't change, and your bucket doesn't need to be public. The smaller sizes themselves stay with us, since we make them from your files.
Files uploaded before you connected stay in Orbit and keep working. Orbit remembers where each file lives.
If the bucket stops working, for example because a key was deleted, uploads stop with a message that an owner or admin can check it under Connections. Files are never quietly saved somewhere else instead. The connection shows Failing: fix the bucket or change its keys, then choose Test.
Move existing files
Choose Move existing files to copy the files already in Orbit to your bucket. It runs in the background: you can leave the page, and the row shows how far it has got. Each file is checked after it is copied, and only then is the copy in Orbit removed. Addresses don't change while files move.
If a file can't be checked, the move stops and says so. Test the bucket, then start again: it carries on where it stopped.
Move back and disconnect
Choose Move back to Orbit to bring every file in your bucket back to Orbit. From then on, new uploads stay in Orbit too. When it has finished, you can choose Disconnect.
You can't disconnect the bucket while files are stored there, because those files would stop working. You also can't change its address, bucket or folder then. You can change the keys at any time: leave Secret empty to keep the one you saved.
Disconnecting deletes the keys from Orbit. Nothing in your bucket is deleted.
Connect a media library
Connect Cloudinary, Bynder or Frontify and every media picker in CMS Orbit, Travel, Commerce, Booking and Presence Orbit gets a From a library menu, and so does Careers Orbit's uploads picker. The library opens in its own picker inside Orbit, so your team searches and browses it as they know it. People sign in to the library there with their own account, so they see what the library lets them see.
Files chosen there are linked, not copied. Each becomes an item in that satellite's media library with the library's address, name, size and alt text if the library has it, so it works in every image field, shows where it is used and goes to the bin like any other file. Websites get the library's own address and sizes: the Delivery API and the SDK ask the library for the width and format they need. Linked files aren't counted in your storage. To change one, edit it in the library: the change shows wherever it is used.
Media libraries need Growth or higher, per satellite. On Starter the menu still lists them and says Growth and up. When one isn't connected, the menu says Connect Cloudinary and brings owners and admins here.
Cloudinary
- In Cloudinary, open Settings, then API Keys, and create a key for Bifröst Orbit.
- In Orbit, choose Connect next to Cloudinary.
- Fill in the Cloud name of your product environment, such as
northwilds, and the API key and API secret from step 1. - Choose Test and connect. Orbit lists one image from your account to check the key.
Bynder
- In Orbit, choose Connect next to Bynder.
- Fill in your Portal address, such as
northwilds.bynder.com. - Fill in either a Permanent token, from Settings, Advanced settings, Portal settings, Permanent tokens in Bynder, or the Client ID and Client secret of an OAuth app with the client credentials grant. Either needs permission to read assets.
- Choose Test and connect. Orbit fetches one asset to check them.
Bynder can only make smaller sizes of a file when your portal has Dynamic Asset Transformation. Without it, websites get the size your team picked.
Frontify
- In Frontify, open your profile, then Personal Developer Settings, and create a personal access token with the
basic:readscope. - In Orbit, choose Connect next to Frontify.
- Fill in your Frontify address, such as
northwilds.frontify.com, and the Personal access token. - Fill in the Finder client ID if Frontify has given you one for your own integrations. Without it, Orbit uses Bifröst Orbit's own.
- Choose Test and connect. Orbit asks Frontify whose token it is to check it.
What the keys are for
The keys you enter are only used to check the connection. Browsing and choosing files happens in the library's own picker with each person's own sign-in, and the keys are never sent to the browser.
Connect Slack
- Choose Connect next to Slack. Slack opens and asks you to add the Bifröst Orbit app to your workspace. Choose the workspace and allow it.
- Back in Orbit, choose Choose channel and pick the channel to post in, such as
#trips-team. - Choose Test and save. Orbit posts a short test message there. Only when that works is the channel saved.
The app can post in any public channel. A private channel appears in the list once someone adds the Bifröst Orbit app to it in Slack.
If Slack isn't available yet, the button says so: we are still setting up the Bifröst Orbit app for Slack.
Connect Microsoft Teams
Teams takes messages through a workflow in the channel.
- In Teams, open the channel, choose Workflows, and add Post to a channel when a webhook request is received.
- Copy the address the workflow shows at the end. It starts with
https://and is on a Microsoft address, such aslogic.azure.comorpowerplatform.com. - In Orbit, choose Connect next to Microsoft Teams, paste the address as Workflow address, and choose Test and connect. Orbit posts a test card to the channel first.
Orbit only accepts workflow addresses on Microsoft's own domains. The address works like a password, so Orbit keeps it encrypted.
What Slack and Teams post
Once Slack or Teams is connected, two things can post there:
- Notices. Under Slack and Teams, choose which notices also go to the channel: Review requests, Review decisions, and Releases and emergency publishing. They come from CMS Orbit and, for job reviews, Careers Orbit. Each notice is posted once, however many people it was sent to, and links to the item in Orbit. New connections post all three until you change them.
- Flows. The flow steps Post to Slack and Post to Microsoft Teams post your own message, such as
Published: {{event.data.name}}, with a link. See Orbit Flows.
Messages only hold the title, the name of the person who did it, the satellite and a link. They never contain the content of a page or a comment, or details about customers.
Connect Vercel or Netlify
CMS Orbit can start a deploy of your website after publishing, so a website that is built ahead of time shows new content without anyone pressing a button.
- Create a hook:
- Vercel: in your project, open Settings, then Git, and create a deploy hook for the branch you publish, such as
main. The address starts withhttps://api.vercel.com/v1/integrations/deploy/. - Netlify: open Site configuration, then Build & deploy, and add a build hook. The address starts with
https://api.netlify.com/build_hooks/.
- Vercel: in your project, open Settings, then Git, and create a deploy hook for the branch you publish, such as
- In Orbit, choose Connect next to Vercel or Netlify and paste the hook.
- Optional: to see how deploys went, add a token that can read deploys. For Vercel, add the Team ID too if the project belongs to a team. For Netlify, add the Site ID from Site configuration.
- Choose Test and connect.
Saving doesn't start a deploy. With a token, Orbit reads the latest deploy to check the token works.
Test starts a real deploy of your website, with what is published now, and may count towards your build minutes. Orbit asks before it does.
Then choose, for each website and environment, whether to deploy after publishing. See Deploy your website after publishing in CMS Orbit.
Back up to your bucket
With your own bucket connected, choose Connect next to Backups to your bucket, then Test and connect. There is nothing to fill in: backups use the bucket's connection.
Each night, from 02:00 UTC, every satellite on Growth or higher writes a copy of your organisation's content to the bucket as JSON files, one file for each kind of content and a manifest.json that lists them:
backups/cms/2026-11-16/for CMS Orbit's spaces, pages, folders, menus, redirects and media detailsbackups/travel/,backups/commerce/,backups/booking/,backups/careers/andbackups/presence/for the other satellites, such as trips and bookings, products and orders, or jobs and candidates
Backups are kept for 30 days; older days are removed from the bucket. Keys, tokens and other secrets are left out. The files themselves, such as images, are not copied again, since they are already in your bucket or in Orbit.
The row shows when the last backup was made. Choose Back up now to make one straight away: every satellite starts within a minute. If a satellite's backup fails, the row says which one; test the bucket, then choose Back up now again.
While backups are on, the bucket can't be disconnected. Disconnect backups first. Backups also hold personal data, such as candidates or customers, for up to 30 days after it is erased in a satellite, so include the bucket in your own data protection records.
Keys and secrets
Keys, secrets and tokens are encrypted when you save them and never shown again. Orbit shows only their last four characters, such as Ends in 7Kq2. You can replace a secret but not read it.
The audit trail
Connecting, changing, testing and disconnecting, starting a move and asking for a backup are recorded in the organisation's audit trail with the person who did it. Choose Connections under What changed to see only those.
Was this page helpful?