Settings → General holds the workspace-wide settings that shape how Spott looks to
your team and to candidates. These settings apply to everyone in your organization.
General settings
- Logo for your workspace. Use a white or transparent background.
- Favicon, the small icon in the browser tab. It has to be an .ico or .png file,
and stay under 100KB.
- Name (Brand name), your organization’s name.
- Workspace currency, the currency every amount is converted to for aggregate
analytics. Placement fees recorded in another currency are reported in this one, using
exchange rates from openexchangerates.org.
- URL (Public slug), the slug used for public-facing pages such as the job portal
and published job adverts, for example
app.spott.io/careers/yourslug.
- Open applications, allow candidates to submit open applications through the
candidate portal without applying to a specific vacancy.
Branding of public pages
Set the Primary color (navbar background), Secondary color (footer
background), and Accent color (the buttons) to match your brand on public pages.
You can also add:
- A Call to Action Button and Navigation Links shown in the public navbar.
- A Consent Disclaimer shown at the bottom of all public forms.
- Social links (LinkedIn, Twitter, Facebook, GitHub, Instagram) shown in the footer.
- A Privacy Policy link, also shown in the footer.
The consent disclaimer becomes a required checkbox at the bottom of every public form,
directly above the submit button:
Company Portal defaults
Every Company Portal is configured per job, which means
someone has to decide the same set of toggles again for every new role. Company
Portal Defaults is where an admin decides those answers once, and every portal
created afterwards starts from them.
The defaults cover the same ground as the per-job controls:
- Candidate visibility: whether new portals show all candidates in real time,
and whether they show candidate stages.
- Portal display: whether scorecards and the salary range are shown.
- Candidate attributes: one default per attribute, in the same list you see on a
job, so a workspace that never shares date of birth can turn it off once instead of
remembering every time.
- The hiring team and the allowed actions given to a client.
You can also set files to be attached by default, which is what makes this worth
doing for most agencies: your Terms of Business goes onto every new portal without
anyone attaching it.
Only admins can set these, and a default is a starting point rather than a lock: each
job’s portal can still be adjusted individually afterwards.
If you change a default that controls what a client can see, open a portal you have
already shared and check its toggles on the job itself, rather than assuming the change
did or did not reach it. Candidate data already shared with a client is not worth
guessing about.