Skip to content
Local environment Preproduction — not production data

Team Settings

In the Settings tab, administrators and developers can manage team information, review the account’s pricing plan and usage, and configure API credentials and dependencies.

Screenshot

The Details tab holds the settings that apply to the whole team. Each setting is a block of its own: what it does on the left, its controls on the right. Changes are kept as a draft until you Save them, except the parent teams, which save one change at a time.

Both are fixed when the team is created and cannot be changed from this page. The slug is what appears in every URL. To rename a team, contact us.

The IANA time zone the team runs in. It is what scheduled processes are interpreted against, and what fcode.team.timezone returns inside a process.

The workspace’s main language. It is the locale used when an execution or a form render does not name one, and the fallback for keys the chosen locale has not translated yet. Left unset, the workspace’s first locale is used. See Internationalization.

Forms always validate their input. When this is turned on, executions started any other way — webhooks, the API, schedules — are also validated against the process’ parameters schema before they run, and one with invalid input fails instead of starting.

The process invoked whenever another process fails, optionally pinned to a version tag. See handling errors. A workspace without processes has nothing to pick yet.

If the handler cannot run — the process was deleted, or the team cannot resolve the version it is pinned to — the failure is kept in the failures store instead, as if there were no handler.

The teams this one inherits processes, modules, variables, locales, dependencies and settings from. Up to five, and cycles are rejected. Their order is their priority: the first in the list wins when two parents provide the same thing.

  • Add parent team opens a dialog to pick the workspace; the new parent goes last. You can pick among the workspaces you belong to, and an operator can search every workspace.
  • The arrows reorder the parents, and each row’s version picker pins it (see below).
  • Removing a parent asks for confirmation first: the workspace stops inheriting its processes, modules, variables, locales and dependencies right away. The settings it took from that parent are kept as the workspace’s own, so they do not change.

Each of these changes saves on its own and reloads the settings above, so while those have unsaved changes the parents cannot be changed: save or discard them first.

Each parent can optionally be pinned to one of its workspace versions — a published tag, or an alias such as stable. A pinned parent contributes only the processes, modules and locales snapshotted at that version, and contributes them with the snapshot’s content, so the parent can keep editing (and even publishing new versions) without changing what this workspace runs. An alias pin follows the alias: re-pointing it in the parent moves every workspace pinned to it. Without a pin the parent resolves live, as before.

Its dependencies follow the pin too — you install the packages that version was published with, not the ones the parent installs today. Variables have no versioned form and always resolve live.

A version or alias that another workspace is pinned to cannot be deleted until that workspace unpins it; re-pointing an alias stays allowed — that is how a new version is promoted.

Because the parent link decides this, an inherited process, module or translation file shows the version it is inherited at as a read-only picker in its editor — the pinned tag, or Live for an unpinned parent — and does not follow the workspace version selected in the sidebar, which only covers what this workspace owns. The editor shows the content that version published rather than the parent’s current draft.

A team with parents also takes five of its settings from them: the timezone, the primary locale, parameters validation, the error handler process and webhook authentication. Each one the team does not set itself comes from the first parent in the list that sets it; when none does, the platform default applies. Like the rest of inheritance only direct parents count, and settings always resolve live — a version pin does not apply to them.

Each of these settings starts with an Inherit from … switch, naming the parent its value comes from (or saying that no parent sets it, so the default applies):

  • On — the team takes the value in effect, shown read-only under the switch.
  • Off — the controls become editable, starting from the inherited value, and what you save is the team’s own value, which wins over every parent.

Turning the switch back on and saving drops the team’s own value; the page then shows the value inherited from the parents. The error handler and webhook authentication can also have no value of their own: turn the switch off and leave the handler empty, or webhook authentication disabled, and the team has none, and inherits none either. The primary locale has no such state — without a locale of its own, a team with parents inherits one.

Removing a parent never changes a setting the team took from it: each one becomes the team’s own, at the same value, and the page shows it with Inherit from … off. Turn the switch back on to take the remaining parents’ value instead. The error handler is the exception when its process came from that parent: the team can no longer run it, so it goes back to inheriting.

Every other setting on this page, and the team’s plan and limits, belong to the team alone.

Turn on Enable global webhook auth and two fields appear, defining the credential that every process webhook set to Use the workspace configuration expects:

  • Webhook variable — the name of the team variable holding the expected token. Only the name is stored here; the value lives in the variable, and a secret variable keeps it out of the dashboard and out of exports. The variable does not need to exist yet.
  • Webhook header — defaults to Authorization, whose value must then be Bearer <token>. Any other header receives the raw value. Use x-factorial-wh-challenge for webhooks that Factorial itself sends, since that sender cannot be told to use Authorization.

Configuring it here means one token protects many webhooks and rotating it is a single change. Each process still chooses whether to use it, in the webhook’s Edit auth option — see webhook authentication for the full request format.

Turning it off removes the configuration. Every webhook that inherits it then rejects all calls with a 403 until it is configured again or those webhooks are switched to their own configuration. A team with parents takes their configuration when it has none of its own — see inherited settings; turning off Inherit from … and leaving it disabled is what leaves it without one.

The Versions tab publishes and manages workspace versions — a single tag applied to every process, module, translation file and dependency manifest owned by the team — and the workspace aliases (such as production) that point at them. Browsing and running a version happens from the version selector in the sidebar.

This area allows you to view and modify your current subscription details:

  • Upgrade to access additional features.
  • See your active plan and its limits.
Screenshot

By clicking the upgrade plan button, any administrator can initiate an account upgrade, unlocking a more powerful version of Factorial Code.

The yeps consumption component display the amount of Yeps consumed in the current billing period and the remaining available Yeps.

Teams are no longer deleted from this page. To delete a team, contact us — deletion results in a complete data wipe and cannot be undone.