Internal Portal
Placeholder image (will be replaced with a product screenshot).
The internal portal is an optional mode that can be enabled per tenant.
It becomes available only when:
- Your account is an internal user
- Your tenant has internal portal enabled
What Changes For Internal Users
Internal portal typically adds additional visibility and controls.
- Internal users can see all candidates, not only candidates shared to the portal.
- Candidate visibility is not restricted by GDPR sharing acceptance.
Internal users may also see additional sorting and filtering options (for example sorting Projects by client).
Internal portal is designed to give recruiters and consultants the same visual workspace as their external stakeholders, while exposing additional operational controls.
Placeholder image (will be replaced with a product screenshot of internal-only functionality).
Internal-Only Actions
Depending on permissions, internal users may be able to:
- Use table view for candidate lists (if enabled)
- Filter by candidate step and portal state
- Perform bulk actions on candidates (send invitation, send interim report email, reject, cancel rejection)
- Sort Projects by client name
- Open EmmyCore and EmmyScore directly from the portal (if configured)
- See a sync status indicator in the header (if enabled)
These capabilities are not controlled by one single switch. A user must be internal, the tenant must allow internal portal, and some actions additionally require dedicated permissions.
In practice, this means two internal users in the same tenant can still see different action buttons depending on their assigned permissions.
If You Do Not See Internal Features
If you are expecting internal features but do not see them, the most common reasons are:
- Your account is configured as an external user
- Internal portal is disabled for your tenant
- The specific action is not granted to your role or account
- The feature is hidden by tenant configuration
In practice, the fastest way to diagnose missing internal features is to check whether the issue is caused by user type, tenant activation, or role permissions.