Frequently asked questions
How do I start?
Follow Getting started. It ends with a working setup rather than a tour. For a first project on a small source, one sitting is enough; 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.
How do I add or remove someone?
See Invite your team. Removal lives in the same settings screen as invitations. When somebody leaves the company, remove them from the project first, then rotate any credential they created — closing an account does not retire the tokens it issued.
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 Fotoslov — переводчик по фото can do.
Can I export my data?
Yes, and Security and data says in which formats. Export before an account closes rather than after.
Which tools does it connect to?
See Integrations. Where no first-party integration exists, the API covers it.
Something looks wrong. 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. Troubleshooting has the full order.
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.