Once a Forge AI feature is deployed, day-to-day management happens on its own page (/portal/forge/your-feature-slug). Each feature gets the same set of tools — submissions inbox, edit, version history, exports.

The feature page tabs

Tab	What it does
Submit	The form your team uses to submit entries
My History	The current user's own submissions
Submissions	All entries from everyone (Manager / approvers only)
Versions	History of feature edits, with revert
Edit Feature	Update the feature's description, fields, or workflow
Settings	Visibility, approvers, archive

Approving submissions

Open the Submissions tab.
Pending entries show at the top with a yellow badge. Click any to see the full detail — fields, calculations, employee comments, attachments.
Click Approve or Reject. A rejection requires a reason; an approval is one click.
On approval, the auto-action runs. For pay-affecting features, the amount appears in next-cycle payroll automatically.

Bulk approve by selecting multiple pending entries and clicking Approve selected. Saves time when you're processing a backlog.

Edit a feature without breaking history

The temptation when you want to tweak a feature is to start over. Don't — you'd lose all submitted entries. Instead:

Click the Edit Feature tab. A chat opens, pre-loaded with the feature's current spec.
Describe what you want to change. For example: "Add a field for project code, required for entries over 20 hours."
Review the diff. Forge AI shows you exactly which fields are added / removed / changed.
Click Save as new version. The feature is updated. Existing entries stay intact (with the old field set); new submissions use the new version.

Version history and revert

Open the Versions tab to see every edit ever made:

Who edited it
When
What changed
A Revert button

Reverting brings back an old version — useful if a recent edit broke something. Existing submissions are preserved.

Export submissions

Click Export CSV in the Submissions tab. The CSV includes every field for every submission, plus status, approver, and timestamps. Useful for:

Sharing with accountants
Importing into spreadsheets for further analysis
Backup before major edits

Change visibility

In Settings on the feature page:

Visibility — Everyone / specific departments / specific roles
Approvers — pick who can approve (defaults to direct manager of the submitter)
Notifications — control which events trigger emails
Archive feature — hides from the sidebar without deleting data. Reactivate any time

Common questions

A user submitted to the wrong feature — can I move it? No — submissions can't migrate between features. Reject the entry with a note pointing them to the right one.

Edits to a feature break old entries. They shouldn't — old entries keep their original field set. If you see a broken old entry, that's a bug; please contact support with the feature slug.

Can I delete a deployed feature? You can archive it (hides from sidebar, preserves data) or permanently delete (wipes everything). Archive is almost always what you want.

A feature is no longer needed but I want to keep its data. Archive it. The data, including all submissions and version history, stays — you can export at any time. Reactivate later if you change your mind.