Admin

In some jurisdictions, imprints are not mandatory. If you leave this field blank, the footer will show no link to the imprint.
Name Active Admin Mod Controls

Authentication Backends

Configure how users can authenticate to your instance. You can enable multiple authentication methods. Password authentication is the default method.

Username/Password (Enabled) The default authentication method using local username and password. Users can register and log in with credentials stored in the database.
Allow users to log in with username/password

Registrations: Open
Change this setting in the Settings tab

New users must verify their email address before accessing their account
Mastodon/Fediverse (Disabled) Allow users to authenticate using their existing Mastodon or other Fediverse accounts. Users receive a verification PIN via direct message to their Fediverse account.
Display name shown on the login page (e.g., 'Login with Mastodon') Allow users to authenticate via Mastodon/Fediverse Default Mastodon server URL (users can specify their own) Number of digits in the verification PIN How long the PIN remains valid
OAuth (Disabled) Enable single sign-on (SSO) with OAuth2/OpenID Connect providers. Useful for integrating with self-hosted identity servers or community authentication systems.
Display name shown on the login page (e.g., 'Login with Community Account') Allow users to authenticate via OAuth Internal identifier for this provider (lowercase, no spaces) OAuth application client ID from your provider OAuth application client secret from your provider Provider's OAuth authorization endpoint Provider's OAuth token exchange endpoint Provider's endpoint to retrieve user profile OAuth permissions to request (comma-separated) Callback URL to register with your OAuth provider
LDAP (Disabled) Connect to an LDAP server to authenticate users with their existing directory credentials.
Display name shown on the login page (e.g., 'Community Directory') Allow users to authenticate via LDAP Hostname or IP address of your LDAP server Select standard LDAP/LDAPS or specify a custom port The root of your LDAP directory tree (e.g., dc=company,dc=com) Service account for LDAP queries (optional for anonymous bind) Password for the bind DN service account LDAP filter to find users. {username} will be replaced with login name LDAP attribute containing the username (typically 'uid' or 'cn') LDAP attribute containing the email address

Instance following

Use this to replicate the items of other instances onto your instance. You can request replication of other servers by using Follow Instance. Under Following instance, you can answer requests from other instances to follow your instance.

Follower Instance0
Following Instance0

Coverage

Click on the map to set a location. Only instances within range can federate items.

Startpage

Clicking a box chooses between active (green) and deactivated (yellow) tab view. Drag and Drop moves boxes to set position of tabs.

About
Featured
Local
All

Units

Set allowed currencies for item creation via a comma-separated list. No input results in a free-text field.

Blocking

Use this to block users or entire instances from communicating with your instance. It is wise to whenever possible only block single users instance-wide. A valid reason for blocking a whole instance might be jurisdiction-wise incompatibilities with another instance.

Use this to upload a CSV-File containing many domains to block. Several blocklists are provided to the public in this format. The first column in the blocklist must contain the domain.

Blocked Instances
Blocked Users

Tests

E-Mail configuration