Organizations

General Settings

The General Settings page allows organization owners to configure the fundamental properties and preferences of their organization. This is where you manage the organization's identity.

Accessing General Settings

Navigation Path:

User Menu → My Organizations → [Select Organization] → Settings → General

Only users with Organization Owner role can access and modify these settings.

Organization Properties Interface

The organization settings interface provides a clean, organized layout for managing your organization's fundamental properties. Here's the structure you'll encounter when accessing the General Settings page:

SettingsChange your organization settings from hereOrganization ConfigurationNameYour Organization NameOrganization name is requiredMonikeryour-organization-idThe moniker is a unique identifier for the organizationDescriptionThis is your organization description. You can use this field toprovide details about your organization purpose, structure, or anyother relevant information.Emailadmin@yourserver.com⚠Danger ZonePermanently remove this organization and all its dataDelete OrganizationSave

This interface preview shows the layout of your organization's General Settings page. Save stores the name, moniker and description. The Email field is not saved in this version.

Configuration Options

Organization Name

FieldTypeRequiredDescription
NameText inputYesThe display name of your organization, shown in the organization menu and lists

Behavior:

  • Cannot be empty: the form shows "Organization name is required"
  • Cannot be changed for default organizations (the field is disabled)
  • There is no length limit

Organization Moniker

FieldTypeRequiredDescription
MonikerText inputYesUnique identifier of the organization, used in its URLs

Below the field, the page shows the resulting address, <server URL>/<moniker>, in green while the moniker is valid and in red when it is not.

Moniker Rules:

  • Required: "Organization moniker is required"
  • At least 4 characters: "Organization moniker should have at least 4 characters"
  • Only lowercase letters (a-z) and numbers, with single hyphens (-) between them. Spaces, uppercase letters, underscores and other symbols are not allowed, and the moniker can't start or end with a hyphen or contain two hyphens in a row. Otherwise the form shows "Only lowercase letters and numbers are allowed" and "Use '-' instead of whitespaces"
  • Unique in the instance. The form checks it while you type and shows "Organization with the same moniker already exists" if another organization uses it
  • Cannot be changed for default organizations (the field is disabled)

Examples: acme, data-team, team2026 are valid; Acme, data_team, -data, abc are not.

Where the Moniker is Used

The moniker identifies the organization in these places:

WhereExampleAfter a moniker change
Application URLs<server URL>/acme/settings/general, <server URL>/acme/<project>/...The page moves to the new address after Save. Bookmarks and shared links with the old moniker stop working
GraphQL APIThe organization argument of the queries and mutations, for example organization(organization: "acme")Scripts that call the GraphQL API must use the new moniker
Dataset and pipeline API endpoints/api/acme/<project>/model/<n>/dataset/<n>, /api/acme/<project>/model/<n>/pipeline/<n>The URL is fixed when the endpoint is created: existing endpoints keep answering at the URL with the old moniker. See API overview
Default organizationThe organization created with a user account uses the username as monikerIts moniker can't be changed

Data, projects, members, roles, jobs and files are linked to the organization itself, not to its moniker, so they are not affected by a change.

Choose a stable moniker, such as the company or team name, and change it only when needed: tell the members and update any bookmarks and GraphQL scripts that use the old one.

Description

FieldTypeRequiredDescription
DescriptionText areaNoFree text about your organization's purpose and structure

The description is optional, can have several lines and has no length limit.

Email

FieldTypeRequiredDescription
EmailText inputNo"Corporate Email Address"

In this version the Email field is not saved and is not used to send any notification.

Organization Deletion

Permanent Action: Deleting an organization cannot be undone. Export anything you need to keep before you delete it.

The Delete Organization section, at the bottom of the page, has a Delete button. Only organization owners see it.

Delete Organization
Deleting this organization will delete all data related with it.
Use it carefully. This action cannot be undone            [ Delete ]

To delete the organization:

  1. Click Delete.
  2. In the Delete Organization: <name> dialog, type the organization name in Type in organization name to confirm. If it doesn't match, the dialog shows "Organization name does not match".
  3. Click Delete this Organization and its data.

A default organization, the one created with a user account, can't be deleted, not even by its other owners: its Delete button is disabled, and the server answers "You can't delete default organization".

What Gets Deleted

Every project of the organization is deleted with all its content, the same way as when you delete a project. Then Gigantics deletes:

DeletedDetails
Projects and their contentModels, rules, discoveries, datasets, jobs, data sources, environments, variables, labels, functions, dictionaries, password managers, API keys and the other project data. See What gets deleted.
Organization rolesThe custom roles defined in the organization.
InvitationsThe pending invitations to the organization.
Organization eventsThe organization's activity events.
The organizationThe organization itself, with its settings and member list.

What Gets Preserved

  • User accounts. Members lose access to the organization, but their accounts and other organizations are kept.
  • Global settings, global variables and licenses of the instance.
  • Other organizations on the same instance.
  • Data already written to your own databases or files outside Gigantics (sinks, exported files).

Security and Permissions

Access Control

Only users with the Organization Owner role can:

  • View the General Settings page
  • Modify organization properties
  • Access the deletion functionality
  • Change the organization moniker

Field Restrictions

SettingCan be Modified byNotes
NameOrganization OwnerCannot be changed for default org
MonikerOrganization OwnerCannot be changed for default org
DescriptionOrganization OwnerAlways editable
DeletionOrganization OwnerRequires confirmation. Not available for default org

Best Practices

Name Configuration

  • Choose a descriptive but concise name
  • Include your company or team name for clarity
  • Avoid internal acronyms that new members won't understand

Moniker Selection

  • Keep it short and memorable
  • Use only lowercase letters, numbers and hyphens
  • Once set, avoid changing it unless necessary: see Where the Moniker is Used

Description Guidelines

  • Include information about organization's purpose
  • Describe the types of projects managed
  • Mention any special compliance or security requirements

Troubleshooting

Can't Save Changes

Problem: Save button doesn't work or shows an error

Solutions:

  1. Verify you have organization owner permissions
  2. Check if the organization is your default organization: its name and moniker can't be changed ("You can't change default organization name", "You can't change default organization moniker")
  3. Ensure the moniker doesn't conflict with existing organizations
  4. Verify all required fields are filled correctly

Moniker Validation Errors

Problem: Won't accept the moniker you entered

Common Issues:

  • Moniker already exists
  • Shorter than 4 characters
  • Contains uppercase letters, spaces, underscores or other symbols
  • Starts or ends with a hyphen, or has two hyphens in a row

Solution: Use only lowercase letters and numbers, with single hyphens between them

Dependencies

Organization settings affect: