Objects
Portal & public exposure
Expose object records safely to customer portal users and standalone public forms.
Portal & public exposure
Object exposure settings decide whether records are internal only, visible to signed-in portal users, or open to anonymous public submissions. Configure these settings deliberately because they change who can create, view, edit, and delete records.
Exposure options
| Exposure | Setting area | What users can do |
|---|---|---|
| Staff only | Object base, table, and role settings. | Staff users manage records in the main workspace. |
| Customer portal | Customer settings: readonly, featured, add, edit, delete, max records. | Signed-in customers interact with permitted records in the portal. |
| Public form | Public flag and public code. | Anonymous users submit records at /form/<code>. |
Configure portal access
- Enable customer access for the object.
- Decide whether customers can add, edit, delete, or only view records.
- Set a maximum record count when submissions should be capped.
- Place the object in the portal menu or a custom portal page.
- Test as a portal user, not as an admin.
Configure public access
- Enable the public flag and public code.
- Review required questions and remove internal-only fields.
- Test the form URL in a private browser session.
- Add automation for acknowledgements, triage, and staff follow-up.