> For the complete documentation index, see [llms.txt](https://docs.feathery.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.feathery.io/platform/collaborative-workflows/collaboration/start-directly.md).
# Start Directly
If you're the first collaborator on the form submission, you can skip the email flow.
You may choose to start your submission directly if you're the first collaborator and you want to invite your collaborators in the form itself via fields.
Clicking **Next** on this step will open up your form and initiate the collaborative submission. Your Feathery account email will be used as collaborator 1's email.
## Invite Additional Collaborators
Once you're in the form, you should make sure your form has button(s) configured with the [Invite Collaborator to Submission](/platform/build-forms/actions.md#invite-collaborator-to-submission) action. Define one action per additional collaborator you want to invite to the submission (so N-1, where N is the total number of [collaborators defined](/platform/collaborative-workflows/collaboration.md#define-your-collaborator-settings)).
If in your collaboration template you specified that collaborators should fill out the form in order, only the next collaborator in line will receive an email invite (and only after you complete your part of the submission first). If order doesn't matter, then all additional collaborators that you've invited will receive an email invite once you've completed your part of the submission.
## Return to Previous Collaborator
You can also use the [Return to Previous Collaborator](/platform/build-forms/actions.md#return-to-previous-collaboration) button action to rewind. For example, if the second collaborator can decide that the first collaborator needs to edit their submission, they could trigger a button on the form with that action to send the submission back to the first collaborator.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.feathery.io/platform/collaborative-workflows/collaboration/start-directly.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
