Skip to main content

Company settings

Configure Company Header and Logo, Change Proteus Email details

Written by James Gold

Summary

Company Settings is the section of the Proteus Admin Console where organisation-wide configuration is managed. This includes the company’s basic identity information and the email settings used for system-generated communications.

Only users with Admin role permissions can access and modify Company Settings. Changes made here apply across the entire Proteus tenant and will affect all users.

To access Company Settings, navigate to the Admin Console from the main navigation menu and select Company Settings.


Basic Information

The Basic Information section displays the core identity details for your organisation’s Proteus account. These settings were established when your Proteus tenant was first created and are used throughout the platform.

Company Logo

The default company logo is configured directly within the Basic Information section of Company Settings. It is uploaded manually and is separate from any logos configured on individual Office records.

The company logo is used in the following places:

  • As the organisation’s default logo across the Proteus interface.

  • On Invoice PDF documents generated by Proteus, where the logo appears as the company’s branding on the invoice.

How to Upload the Company Logo

  1. Navigate to Admin Console > Company Settings.

  2. On the Basic Information tab, locate the Company Logo field.

  3. Select the upload image option and choose the logo file from your device.

  4. Save the changes. The updated logo will be reflected across the platform and on Invoice PDFs immediately.

NOTE: The company logo must be uploaded manually via the Basic Information tab. It cannot be set or changed from within individual Office records.

Company Name

The default company name displayed in Proteus is the name that was entered when the Proteus account and URL were first created. This name is used in system-generated documents and communications as the organisation’s trading name.

Timesheet Grace Period

Timesheet locking is a protective feature applied automatically to all users. On a weekly basis, timesheets automatically lock after midnight on Friday, ensuring that any changes made after the reporting week has closed require explicit approval from the Project Manager - only they are able to unlock a timesheet once it has been locked.

This deadline can be extended if needed, using the Timesheet Grace Period setting configured in the admin console. This allows users a defined number of additional hours beyond Friday midnight to submit or amend their time before the lock takes effect.

If no value has been set for the Timesheet Grace Period, automatic timesheet locking will not apply.


Proteus Emails

Proteus generates a number of system emails automatically as part of its workflows for example, timesheet reminders, approval notifications, and action required alerts. By default, these emails are sent from Proteus’s own email address: noreply@proteus-work.com.

The Proteus Emails settings allow organisations to configure a custom sending email address, so that system emails appear to come from their own company domain rather than from a Proteus address. This can improve email deliverability and ensure communications align with the organisation’s branding.

If no custom email settings are configured, all system-generated emails will continue to be sent from noreply@proteus-work.com. This is the default behaviour and requires no action to maintain.

How to Configure Proteus Emails

  1. In the Admin Console, navigate to Company Settings.

  2. Select the Proteus Emails tab.

  3. Enter the required SMTP configuration details in the fields provided (see Email Configuration Fields below).

  4. Select Save to apply the settings.

  5. Proteus will automatically send a test email to the logged-in admin user to verify the configuration.

  6. Confirm receipt of the test email. If the email is not received, review the settings with your IT team and re-save to trigger another test.

Email Configuration Fields

The following fields are available on the Proteus Emails configuration form. These settings are provided by your organisation’s IT team or email service provider:

Field

Description

From email address

The email address shown as the sender in the recipient’s inbox. For some mail server configurations this must match the SMTP username exactly. For others, it is possible to send from any email address on the domain.

From name

The display name shown as the sender in the recipient’s inbox (e.g. Proteus — Your Company Name).

SMTP mail server

The URL of the mail server responsible for sending the emails. This will look like a domain name, for example: smtp.xergy.com.

SMTP port

The port number used to connect to the mail server. This normally corresponds to the security mode selected. Common values are 25, 465 or 587.

SMTP security mode

The encryption method used for the connection to the mail server. Options are None, SSL, TLS or Auto. Set this according to what the mail server supports.

SMTP username

The username used to authenticate with the mail server. This may be the same as the From email address, or it may be a separate account username depending on the mail server configuration.

SMTP password

The password associated with the SMTP username, used to authenticate with the mail server.

TIP: If your organisation uses Microsoft 365 or Google Workspace as its email provider, your IT team will be able to supply the correct SMTP settings for those platforms. Common configurations include:

• Microsoft 365: SMTP server smtp.office365.com, Port 587, TLS encryption.

• Google Workspace: SMTP server smtp.gmail.com, Port 587, TLS encryption.

Ensure that the sending account has SMTP AUTH enabled and that any multi-factor authentication or app password requirements are met before attempting to configure these settings in Proteus.

Configuring a Custom Email Address

Configuring custom email settings requires technical SMTP credentials that are typically only available to your organisation’s IT team. There are multiple configuration variations and incorrect settings can prevent system emails from being delivered. It is strongly recommended that an IT professional within your organisation is involved in this process.

Did this answer your question?