Welcome to Selfform

Selfform is for building the applications your team works with —a help desk, purchase requests, time off, maintenance, inventory— without writing code. You decide what gets captured, who sees it and what happens to it; Selfform keeps it, shows it and lets the right people know.

Words you'll see

• Application: everything one process needs, a "Help desk" say. It shows in the menu on the left.
• Entity: the kind of thing an application keeps, like "Ticket" or "Order". An application can have several.
• Record: each ticket or order someone enters.
• Field: each piece of a record: a name, a date, a file, a list of options.
• Page: each screen of the application. It can be a form to enter records, a table to search them, a board, a calendar, a Gantt chart or a dashboard with charts.
• State: where a record stands, like "New", "In progress" or "Solved".

Getting started

1. Create an application with + New application, in the menu on the left. You can start from a template that's already built and adjust it, or from scratch.
2. Build the form. Add the fields you need, name them and arrange them as you like. The preview shows how it will look. See the form builder.
3. Enter a few records to try it out.
4. Add more pages: a table to search, a board to move records between states, or a dashboard with charts.
5. Invite your team from Access, on the application's page, and choose what each person may do. See access control.
6. Once it works, let Selfform do some of the work: transitions to put the steps in order, automations so things happen on their own, and notifications to let people know.

Reading the docs

The menu on the left has a page for each part of Selfform. The first ones explain how an application is built: the form, its fields and how they behave. Then come the pages to see and work with records, and last what happens behind the scenes: transitions, automations, notifications, access and data sources. Under Field types there's a page for each field, with an example you can try right there.

Many examples on these pages are real: type into them, drag fields or filter a table without worry, nothing is saved.

Troubleshooting

• I don't see an application or a page. Someone has to give you access. Ask whoever manages the application to invite you, or to check your role.
• A field won't let me type. It may be read-only for your access, locked because a lookup fills it, or a field that works itself out, like a formula or a folio.
• I can't save. Look at the red messages beside the fields: usually a required one is empty or a value is out of range.
• I can't move a record to another state. If the entity has transitions, records only move along them, and each says who may use it. Some also wait for an approval.
• An automation did nothing. Open its Runs: they say when it ran, whether it was skipped because its condition didn't hold, and why it failed.

FAQ

Do I need to know how to code? No. Everything is built with clicks: adding fields, picking options and arranging pages. Formulas look like a spreadsheet's, and they're optional.

Can I change an application that's already in use? Yes. Add fields and pages whenever you want. Saved records aren't lost, and each one remembers the version of the form it was entered with.

Is anything deleted when I archive it? No. Archiving takes it out of sight, but it can be restored.

Can I bring in data I already have? Yes. A table can import a CSV file, and an admin can connect other systems so forms fill fields on their own. See data sources.

Is there someone to ask? Yes: the Help bubble, bottom right, opens a chat that answers from these docs. Ask in your own words.