Skip to main content
Use this checklist when your organization adds a team to Kadoa. Each step says who does it: you (the team’s owner) or your Kadoa customer success engineer (CSE).

​
1. Set up the team

  1. Choose the team name. It appears in the team switcher and in every notification.
  2. Name an owner on your side. Your CSE is the contact on Kadoa’s side.
  3. For each dataset, decide whether it is scheduled or real-time. Scheduled workflows run at set times and deliver complete runs. Real-time workflows watch a page and send each change as it happens. See Monitors.
  4. Send the team name, owner, and dataset list to your CSE.
Your CSE creates the team and makes your owner its Owner. If any dataset is real-time, your CSE also turns on real-time delivery for the team. The owner then invites members and assigns roles. See Members and roles. If your organization uses SSO, SCIM, or an IP allowlist, set them up for the new team too.

​
2. Connect delivery

​
Scheduled datasets

  1. Ask your CSE for Kadoa’s AWS principal ARN.
  2. Prepare an S3 bucket with that ARN in its bucket policy. The Amazon S3 guide has the policy.
  3. Send the bucket name, region, and prefix to your CSE, who sets up the destination.

​
Real-time datasets

  1. Create an API key for the new team in Settings > General. Only Admins and Owners can do this.
  2. Connect your WebSocket receiver with that key. A receiver only gets events for the team its key belongs to, so a key from another team does not work.

​
3. Build the workflows

Members build the workflows with the agent, or ask your CSE to build them. If many workflows collect the same kind of data, create a template first so they share one schema and one set of rules. Real-time workflows need a notification channel. For a WebSocket receiver, create a Websocket channel in Settings > Notifications and select it when you create each workflow.

​
4. Confirm the first data

  • Scheduled: after the first run finishes, confirm the first file arrives in your bucket under the agreed prefix.
  • Real-time: open a real-time workflow’s Notifications tab, open its data change notification, and select Send test. Confirm the test event reaches the end of your chain, for example a Slack channel. The test uses sample data, not your records.

​
5. Book a teach-in

The teach-in is optional and takes 15 minutes. We recommend it. Your CSE walks the team through the dashboard, learns its use cases, and becomes its first contact for questions.

​
Checklist

  • The team exists, with a named owner and CSE.
  • Every dataset is marked scheduled or real-time.
  • Members are invited with the right roles.
  • Scheduled: the first file is in your bucket.
  • Real-time: a test event reached your alert channel.
  • The teach-in is booked or skipped on purpose.