Something not working, or not sure how to do something? Here is where to reach us, and a few things worth checking first.
The fastest route for anything account-related, billing, or a problem you would rather not discuss in public.
support@cruss.ioProblems with the editor extension — installing, connecting your account, or sending requests. The listing has a Q&A tab where answers stay visible to everyone who hits the same thing.
Open the Q&A tabWorkspaces, environments, local API testing, the editor extension and organisations are all covered. Most questions are answered there faster than we can reply.
Open documentationThese four cover most of what people run into. Each links to the part of the docs that explains it properly.
Your token has a limited lifetime. Open the Cruss panel, choose Disconnect account from the workspace dropdown, then Connect account again.
Extension docs →Browsers block requests from cruss.io to localhost. Run the Cruss Agent, or use the editor extension — both send requests from your machine instead.
Local API testing →No environment is selected, or the selected one does not define that variable. Pick an environment from the ENV selector, or create one with the variable in it.
Environments →Workspace roles are enforced on the server. Viewers can send requests but not change them — ask a workspace admin to change your role.
Workspaces & teams →Include these and we can usually reproduce it on the first try, which is the difference between a fix this week and a conversation that takes three days.
Tell us what you are trying to do, not only what you want built — the underlying problem is usually the more useful half, and sometimes there is already a way to do it. Email support@cruss.io with “Feature request” in the subject.