CredoID

Settings

General settings

General

General settings for e-mail, devices and credentials.

Card Formats

Various supported card formats can be enabled/disabled for CredoID system. Disabled card format will be not accepted by CredoID.
Only single same bit lenght format can be enable at a time.

Maximum of 8 card formats are supported by the controllers.

card_formats.png

Press Save to save enabled formats. Synchronization of devices will be required.

HID Aero support up to 8 facility codes per controller.
Mercury support up to 16 facility codes per controller.

If the format supports facility codes but none are specified - facility code will be ignored when the card is read.

Custom card formats

"Create card format" window will open once "Create card format" or "Duplicate" is clicked.

custom_card_format.png

  1. Provide a Name for Your Card Format
  2. Define the Total Bits
  3. Configure the Card Format:
    • Bits are displayed as numbered blocks (e.g., 1, 2, 3 etc.).
    • Click on each bit to define its role.
    • Click on a role to assign it to selected bits. The selected role will appear as a color dot on the bit.
  4. Review and Save the Configuration

Multiple bits can be selected while holding "Ctrl" button.
Range of bits can be selected while holding "Shift" button.

Excluded events

Events can be filtered and excluded either completely or just from archive only.

settings_general_excluded_events.png

Excluded events won't be saved to database therefore some disk space will be saved.
Past events will not be affected by this setting.

Notifications

To enable sending notifications by e-mail - e-mail provider has to be added.

add_email_provider.png

This will be used to send out notifications, QR codes and "Origo Wallet" invitations.

Click "Add e-mail provider" and configuration menu will open.

notifications_email_provider.png

Google requires to use app password for gmail.

QR Codes can be sent out only via default provider.

Once details are correctly filled - click "Test".
If the connection is successful - you can enter your e-mail in "Test e-mail" field and click "Send test message" to verify that it is working correctly.

notifications_email_provider_test2.png

User Import & Reset

user_import_reset_csv_delimiter.png

License Owner

Enter license owners name and it will be shown in main menu instead of "License".

license.png

Mobile ID

Mobile ID providers can be added in this section. Also, you can check the current connection status, edit provider or remove it.
Please follow further instructions on how to setup and issue Mobile ID

mobileid.png

Password policy

Starting from version 4.16.140 release, we are introducing a password policy settings along with password security improvements.

passwordpolicy.png

Server URL

serverurl.png

Public base URL of this CredoID server (e.g., https://credoid.example.com). Used to register webhooks with external credential providers for instant credential status updates. Otherwise, statuses are synced via periodic polling.

Parking

Parking occupancy limiter is a control feature made to regulate the flow of vehicles. It evaluates vehicle flow over a rolling time window and prevents sudden surges by temporarily restricting access when approaching thresholds.

pol_settings.png

Backup & Restore

Create and restore backup and set automatic backups. Backup will consist of current database snapshot, configuration files and media such as profile images, map backgrounds etc.

backup.png

Create button will instantly create a backup.
Restore button restores data from a selected backup.
You can also enable automatic backups and select how often they will be created.

Default backup storage directory is C:\ProgramData\Midpoint-Security\Backup.
It can be changed by editing backup path field.

backup_path.png

Backup should be restored only for the same version. Restoring previous backup on top of newer CredoID might break functionality.

Backups can be downloaded by clicking download.png in the actions column.
To delete backup click on redbin2.png in the actions column.

Clean-up

Set automatic clean-up for events, users and backups.
CredoID will run automatic clean-up check each hour. Clean now allows to start check right away.  
Any of the modified settings be saved by clicking Save before clicking Clean now.

Devices

Global device related settings such as PIN code length, OSDP reader LED & Beeper templates & Automatic device synchronization.

PIN Readers

Set PIN code length accepted by CredoID and readers with keypad (if supported).

LED & Beeper

Using OSDP readers in the system allows you to configure LED & Beeper behaviour. You can have up to 3 templates that can be configured and applied to each door.
"Default template" is configured to match controller manufacturer default configuration and is used as default when creating new door.

This feature is supported only with HID Aero and Mercury controllers.

When using "Card & PIN" reader mode - reader goes into "PIN only" mode after swiping card first or into "Card only" mode after entering PIN first. LED changes accordingly.

Available colors:

Auto synchronization

Automatic synchronization can be configured here.

autosync.png

Memory allocation

Supported only with Mercury controllers. Will require each device to be fully synchronized.

Mercury controllers allow administrators to adjust the number of access levels assigned to each cardholder. Memory allocation is shared between cardholder capacity and access level storage, creating a trade-off between these two resources.

memory_allocation.png

Only devices that have been added to the system are displayed here.

This flexible memory allocation enables system optimization based on site requirements and user access complexity.

MQTT Server

CredoID runs an embedded MQTT broker inside the backend. External devices (e.g. Axis cameras) connect to CredoID.

mqtt_settings.png

Logs

Change logging level and download logs.

Sorting from highest to lowest, logging level can be set to:

Logs can be downloaded by clicking download.png in the actions column.
Stored logs can be found at C:\ProgramData\Midpoint-Security\CredoID Service\Logs

This information is necessary to provide when requesting CredoID support. Please enable "Debug" if you have a repeating issue and submit the logs to our support desk.

API Tokens

Personal access tokens let external applications call the CredoID API on your behalf. Each token is tied to a role and location scope, so integrations only get the permissions you assign.

Only operator administrators can create and manage API tokens.

Token creation

1. Create a role with the required permissions

Go to Users → Roles and create a role with the permissions the integration needs (for example, read users, control doors, or view events).

Use a dedicated role per integration when you can — it keeps access easier to audit and revoke.

2. Create a token

Go to Settings → API Tokens and click "Add" to create a new token:

apitokencreate.png

3. Copy and store the token

After creation, copy the generated token immediately. It is shown only once and cannot be retrieved later.

The token list shows a short suffix so you can tell tokens apart without exposing the full value.

apitokencreated.png

4. Use the token in API requests

Send the token as a Bearer token in the Authorization header:

Authorization: Bearer <your-token>

Use it the same way as a JWT from a normal login. The token stays valid until it expires or you delete it.

Security notes