ApplySG Portal (Public Officers) template
The ApplySG Portal (Public Officers) template is the starter configuration for government internal workflows. Applicants are whole-of-government (WoG) users. The template has one form type and one predefined role, and it expects you to define your own states with the State Builder. This page also lists the portal’s capabilities.
Feature availability: The ApplySG Portal (Public Officers) is in Beta.
Portal capabilities
| Feature | What it does |
|---|---|
| Closed invitation for WoG applicants | Backoffice users with the Invite permission send personalised email invitations. Only the invited user can accept and begin a submission. Refer to Invite applicants to a closed scheme. |
| Team-based submissions for WoG applicants | Lets WoG applicants work on a submission as a team. The creator becomes the default team member, and collaborators join with scoped roles. Every required role must be filled before the submission can move forward. Refer to Configure team-based submissions. |
| Listings URL filtering | Filters the scheme listing page through URL parameters such as ?schemes[]=<RESOURCE_ID> or ?agencies[]=<AGENCY_CODE>. Refer to Filter the open listing by URL. |
| Segregation of agency listing | Lets agency users see and apply to listings from their own agency and other agencies that you whitelist. Refer to Scheme settings. |
For the sign-in methods, refer to Login methods.
Form types
| Form type | Kind |
|---|---|
| Application | Parent |
You can add custom child form types. Refer to Manage form types.
Form roles
The template includes one predefined role. A form role can do the following.
| Action |
|---|
| View submissions |
| Accept a submission from the unassigned pool |
| Make a recommendation and upload letters to the applicant |
| Return for edit |
| Approve a recommendation |
| Reassign submissions |
States
The template starts with a single state.
| Applicant state | Backoffice state |
|---|---|
| Draft | Draft |
Define the other states yourself in the State Builder. Refer to Add and edit states.
Segregation of duties
Scheme owners should make sure that duties are separated. Evaluation and approval should be done by different officers. Officers who hold the Manage Permissions scheme permission should not also hold a processing role. Refer to Scheme permissions.
Clause 1.4/S7 of the Instruction Manual for Cloud (IaaS and PaaS) Security requires agencies to enforce segregation of duties and least privilege. Appropriate authorities must authorise and approve access rights, and grant them according to each user’s role and responsibilities.
Constraints and limitations
| Constraint | Detail |
|---|---|
| Template | This page applies to the ApplySG Public Officers Starter Template only. |
| Backoffice guide | The portal has no pre-built backoffice guide. |
| Beta | The portal is in Beta. |
Related content
- Dashboards: what the dashboards show.
