Skip to main content
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.
  • 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.
  • Maximum company hierarchy depth, how many levels a company hierarchy may go down, chosen from a list starting at two. Groups that are already deeper than the value you pick are kept, and can only be shrunk until they are back within it.
  • Hide closed jobs in autocomplete, keep closed jobs out of search suggestions and job pickers across the workspace.
  • Default job description language, the language used for a new job description when no language is chosen on the job itself.
General settings with brand name, public slug, and open applications

Speculative Presentations

Speculative Presentations, “Allow users to create speculative presentations”, is on by default. Switch it off if your team never presents candidates without a vacancy, and the feature disappears from the interface rather than sitting there unused:
  • the Speculative Presentations tab under Jobs, and the Speculative tab on candidates, contacts, and companies
  • Add Speculative Presentation on records, the Create Speculative Presentation bulk action, and the switch in the present dialog
  • Speculative Presentation Stages under Settings → Stages
  • the speculative campaign type, and the two speculative triggers when you create an automation
Nothing is deleted. Automations that already use a speculative trigger keep working, and existing presentations come back when you switch it on again. Changing it needs the permission to manage the workspace. See presenting candidates.

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:
The consent checkbox at the bottom of a public application form
Public page navigation, consent disclaimer, and social links

Email editor colors

Email editor colors is a separate palette for the emails you design in Spott. Click Add color, enter a hex code, and it appears as a swatch in the email editor’s color picker, so nobody has to remember or paste your brand’s exact shade of red. The palette applies to two editors only: the Marketing email builder and the Company Portal invite email. It does not change the Primary, Secondary, or Accent colors of your public pages, and those do not feed into it.

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.
Company Portal Defaults, with the candidate visibility and portal display toggles applied to new portals
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. The rejection and application label toggles are not here: they start off on every new portal and are switched on per job.
  • 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.