Getting set up#

How do I start? Follow Getting started. It ends with a working setup rather than a tour.

How long does setup take? For a first project on a small data source, one sitting. Large or unusual migrations take longer, so ask us before you plan around a date.

Do I need a developer?

Fill this in. "No code required" is the single easiest claim to get wrong, and a reader who disproves it on day two remembers. Say which parts need engineering help and which do not.

Accounts and access#

How do I add or remove someone? See Invite your team. Removal lives in the same settings screen as invitations.

Someone left the company. What do I do? Remove them from the project first, then rotate any credential they created. Closing a person's account does not retire the tokens they issued.

Plans, data and limits#

What are the limits? Ask us and we will give you the numbers that apply to your plan. The shape of them is described in What docs can do.

Can I export my data? Contact us and we will tell you exactly which formats are available today. We would rather answer precisely than promise a format that does not exist yet.

When something goes wrong#

The product is behaving strangely. What should I send you? Three things, and they save a day of back-and-forth: what you expected, what happened instead, and the exact time it happened. A screenshot of the whole window beats a crop — the surrounding state is often the clue.

Is there a status page?

Fill this in: link it here if you have one. If you do not, say how incidents are announced instead. Silence on this question reads as "nobody is watching".

Adding to this page#

The rule that keeps an FAQ useful: when a question arrives for the second time, write the answer here instead of answering it again. Keep answers under a hundred words — anything longer wants a page of its own.

Next steps#

• Getting started — the setup path.
• What docs can do — capabilities and limits.
• Invite your team — access and roles.