Every submission that arrives on a form carries a status. Vome ships with six default statuses, and you can create as many of your own as you like, each with its own colour. Together they act as an internal applicant tracking system for the admin team running your recruitment process.
This article covers the statuses themselves: what they are, how to build your own set, and where they show up. Making a status actually do something, such as assigning a sequence when someone is accepted, is covered in a separate article linked at the bottom.

Six, available on every form:
You cannot rename or recolour the six defaults, but you can hide the ones you do not use, reorder them, and add your own alongside them.

Yes, as many as you want. A custom status is a name plus a colour, so your table reads at a glance instead of forcing everything into Accepted or Rejected.
Common examples are Interview booked, Waitlisted, Selected, Not selected, Needs documents, and Archived.
To create one:
They are the two tabs at the top of the Manage submission statuses window, and they answer two different questions.
Global set is your organization's whole status vocabulary: every default status and every custom one you have created. Adding, editing, deleting, reordering and hiding a default all happen here, and they apply everywhere.
This form is about one form only. It shows the statuses currently offered on that form, and lets you hide the ones that form does not need. Hiding something here changes nothing on any other form.
The practical effect is that a General Application can run on New, In Review and Accepted while a waiver form runs on its own vocabulary, without either form taking options away from the other.
Yes, and hiding is almost always better than deleting.
Each tab has an Active and a Hidden list, and every row has a show or hide control. On the Global set tab, hidden statuses are grouped under Default statuses and custom ones below them.
Two things to know about hiding:
Yes. On the Global set tab, drag the rows into the order you want. Defaults and custom statuses sit in one single list, so you can slot your own statuses in between the built-in ones rather than having them appended at the end.
That order is organization wide. It drives the dropdown on every form, the bulk status menu and the filters, so the sequence your team learns is the same everywhere. Ordering is set only on the Global set tab, not per form.
In five places, all on the form's submissions table:
Custom views are worth calling out. Because your own statuses appear in the view's status filter alongside the defaults, you can build a view such as "everything except Archived" and have it load that way every time you open the form.
No. On their own they are for tracking and segmentation: a label and a colour that tell your team where someone stands.
What makes a status act is a rule you attach to it on the form. Reaching a particular status can notify your admins, email the person, or assign them to a sequence or an opportunity. This is how most teams run a screening process: interview, set the status, and let the status carry the person forward.
It is removed from your organization immediately, and any submission sitting in it falls back to its underlying default status.

Full admins can do everything described here. For custom admin roles, two separate permissions apply:
So you can let a coordinator move applicants through your process without letting them change the process itself.