Global Settings

Global Settings let administrators configure the whole Gigantics instance. Only users with the Root role can open them.

Accessing Global Settings

1. Click your user avatar in the upper right corner.
2. Select Global Settings in the menu. The option is only shown to Root users.

The Global Settings sidebar has these sections:

Global Settings
+-- General          Server and email information
+-- Authentication   Sign-in and sign-up methods
+-- Licensing        Licenses and taps
+-- About            Instance information
+-- Variables        Global variables for all the projects
+-- MCP              Remote access for AI assistants

General

The General page ("These values come from the Gigantics configuration file and can only be changed there") shows, read-only:

To change them, edit the configuration file and restart Gigantics: see Server configuration and SMTP configuration.

Authentication

The Authentication page ("Change the way users login into Gigantics. Use your LDAP system or change the user sign-up system of your instance") has three sign-in methods. The change is saved as soon as you select an option.

( ) Use LDAP Server                            [Configure]
( ) SAML 2.0 (IdP Single Sign-On)              [Configure]
(o) Email and password
    [ No restrictions                     v ]

Sign-up Options

When Email and password is selected, choose how new users can register:

With Custom domains, the server checks the part of the email after the @ against the list. The comparison ignores case and spaces, and a leading @ in a domain is ignored, so Example.com and @example.com both allow ana@example.com. Subdomains must be listed on their own: example.com does not allow ana@mail.example.com. A sign-up from another domain fails with "You can't sign up with this email domain. Please contact us for help". Users who have been invited to an organization can sign up with any email.

With Disabled - Invitation only, a sign-up without an accepted invitation fails with "You should have an invitation to sign up. Please contact us for help".

Both options also apply to the first login with a third-party provider (Google, Github or Slack) or SAML, which creates the user: a new user that is not allowed to sign up is not created and sees the same message on the Authentication Error page. Users that already exist can still sign in with a provider.

Third-Party Authentication Providers

The Providers configuration panel has one section per provider. Each provider works independently:

Get the client ID and secret from each provider:

• Google: Using OAuth 2.0 to Access Google APIs ↗
• GitHub: Connect your app to GitHub ↗
• Slack: Slack - Using OAuth 2.0 ↗

When at least one provider is enabled, users see a Connected Accounts section in Preferences → Security ("Security Settings"), where they can manage the providers linked to their account.

LDAP

Click Configure next to Use LDAP Server to open the LDAP server settings panel:

Click Test to check that Gigantics can connect to the server with the bind DN and password. Click Save to store the settings: saving also selects LDAP as the sign-in method.

SAML 2.0

Click Configure next to SAML 2.0 (IdP Single Sign-On) to open the SAML 2.0 configuration panel:

Licensing

The Licensing page ("Manage licenses from here") has two tabs, Licenses and Taps, and an Add license button.

Licenses Tab

Use Search for a license to filter the list. By default the list only shows active licenses: check Show expired and cancelled licenses to see all of them, including invalid ones.

The actions available on each license are:

After a removal, Gigantics shows "License removed". The taps that were using the removed license lose it.

Only master, expired and invalid licenses can be removed this way. For other licenses the server answers "Only a master or invalid license can be removed this way".

Renewing a License

A subscription license can be renewed during the last 30 days before it expires, and at any time after it has expired. The Renew / Update button appears when the license enters this window. Gigantics asks the subscription service for the current license of your plan and replaces the stored one.

• An expired license is shown with the Expired status (not as invalid) and can still be renewed, as long as it is a genuine license for this instance.
• Before the window opens, the server rejects the renewal with "This license can only be renewed during the last 30 days before it expires".
• If the subscription has not been renewed yet (for example, the payment is pending), the service returns the same expired license and Gigantics answers "This license has already expired". The stored license is not changed.
• If you received a new license string (for example, for a license that is not a subscription), add it with Add license and remove the expired one.

Summary

When there is no master license, the Licenses tab also shows a Summary with one card per license tier and the number of taps of each tier:

Taps Tab

Lists every tap of the instance with its Name, Driver type, License Type, Organization, Project and Current license. Use Search for a tap to filter the list.

Adding a License

Click Add license ("Add an existing license or create a new one"):

• I have one or more licenses: paste the license string and click Validate and add.
• Get new licences: choose the taps and the Billing period (Monthly or Yearly), then click Checkout.

About

The About page ("Gigantics instance information") shows the Gigantics Info table. It is useful when you contact support.

Variables

The Variables page ("Define variables and use them in your functions") manages the global variables. They are available in every project, and a project variable with the same name overrides them. See Variables.

MCP

The MCP page ("Let remote MCP clients administer this instance with an API key") turns on the remote MCP endpoint and manages the MCP API keys that AI assistants use to connect to it.

See AI Administration (MCP) and Connect with an MCP API Key.

Best Practices

Configuration Management

1. Document Changes: Keep a record of configuration changes and their rationale
2. Test Settings: Apply changes in a test environment before production
3. Backup Configuration: Keep a copy of the configuration file before major changes

Security Considerations

1. Principle of Least Privilege: Only enable the sign-in methods and providers that you need
2. Regular Review: Periodically review authentication methods and user permissions
3. Use Secret variables: Store passwords and keys used by functions as Secret global variables
4. Review MCP API keys: Delete the keys you no longer use and give every key an expiry date

Troubleshooting

Common Issues

Error Banner and Debug Information

When a request to the server fails, the page shows a red banner with the title "<operation> failed (<status>)". The banner has these buttons:

The message starts with an error id. The server writes the same id in its log, next to the full stack trace, so you can find the matching log line.

The banner is not shown for validation errors, permission errors or missing items, which show their own message. If the server can't be reached, Gigantics shows "Connection error. Server is not available".

If a page can't be displayed at all, it shows "This page couldn’t load" with a Reload page button. Navigating to another page also recovers.

Getting Help

1. Check the server log for the error id shown in the banner
2. Verify your configuration settings
3. Contact support with the downloaded report and the information from the About page