Add a Screen to Skills Workflow
When a team works from a view the standard screens do not give them, ask your AI tool for it: the team's home page, a tab on every job, an entry in the menu. The AI tool builds the screen and publishes it inside Skills Workflow, where your team already works.
Availability
Available when screens are turned on for your tenant; ask the Skills Workflow team. The screen is built as a small code project, so ask for it in a tool that works on code, such as Claude Code, Codex or GitHub Copilot, with the Skills Workflow connector added.
Where a screen can show
| Place | What the user sees |
|---|---|
| Menu | An entry in the Pages group, or in the menu group of a document type such as Job or Project. It opens as its own screen or in a popup. |
| Document | A tab on the detail and on the preview of every document of one type. The screen knows which document it is on. |
| Home | The user's home page. It takes the place of Home workspaces; with several, the lowest order wins. |
| Maintenance | A tile in Maintenance, opening the screen inside it. |
Tell the AI tool where the screen goes, its title in each language your team uses, and which roles see it. With no roles, everyone sees it. Roles marked mandatory are all required; of the others, any one is enough.
Rules and behaviour
- Every publish is a new version. A published version never changes, and a fix is always the next version.
- One version is live at a time, and users get a newly live version within about a minute. Making an older version live again is the way back.
- Published versions cannot be deleted. To take a screen away from everyone, ask your AI tool to publish a version marked inactive.
- The screen reads data with the permissions of the user viewing it.
- Users blocked by missing timesheets do not see the screen unless you ask for it to show to them.