Submit
Submit objects through company workflow and ownership rules.
Related guide: Actions.
The Submit action sends an object back up the approval chain once work has been completed.
It is usually used after something has been assigned.
How it works
When you click Submit, the object is sent back to the person who assigned it to you so they can review it.
If the object wasn’t assigned to you by someone else, submitting it will send it to the company instead.
This ensures that all work follows a clear approval path, whether it’s delegated work or something you created yourself.
Assign and submit
Assign and Submit work together.
- Assign passes the object to someone to work on.
- Submit returns it up the approval chain once that work is ready.
For example, one person assigns an object to another. The second person works on it, then submits it back for review.
What submit means
Submitting an object signals that it is ready.
Depending on the situation, this might mean:
- Work has been completed.
- Something is ready for review.
- A decision is needed before moving forward.
Confirmation and outcomes
In some cases, submitting may ask for confirmation, especially if it affects ownership or important values.
Once submitted, the object is:
- Sent back to the person who assigned it, if it was assigned to you.
- Sent to the company, if you are submitting your own object.
From there, it can be reviewed, approved, or progressed further.
When to use Submit
Use Submit when you’ve finished your part of the work and want to pass it back up the approval chain.
For example, you might:
- Submit work back to the person who assigned it once it’s ready for review.
- Submit a task after completing it so it can be checked or approved.
- Submit your own object to the company once it’s finished.
Submitting completed objects helps keep your workspace focused on active work. Once something is done, submitting it moves it out of your active workload so you can focus on what’s still in progress.
Summary
Submit sends work back up the approval chain for review, approval, or the next step.
It completes the loop started by Assign and helps move objects through the workflow.
Read next: Resources
Continue to Resources.