Manage insideBase

Manage users, technical access and settings for your team. Check the active workspace before making changes.

Requirements and permissions

The overview and API-key list require management.read; user management requires users.manage. Changing API keys and central settings requires settings.manage; opening the settings page also requires management.read. History requires settings.manage. Personal workspaces have no team management.

Step by step

Open team management

1. Open Management in the navigation.
2. Check the active workspace and usage overview.
3. Choose Users, API keys or Settings for the change you need.

The overview shows team members, contacts, storage usage and shared mailboxes. Usage figures support administration and capacity planning; available data depends on enabled modules.

Manage users

1. Open Management → Users and search for the email address before creating an account.
2. For an existing account, choose Invite user, enter their email address and select User or App admin. Confirm the invitation.
3. To create an account, choose New user. Enter email, first name and last name; check language, timezone and Active status. Enable SSO only only for a configured SSO account.
4. To change an existing user, open Edit. The App admin checkbox controls management access. Complete reauthentication if requested.
5. Save and check the list. Reopen an existing user if you need to send another invitation or perform an authorized two-factor reset.

Users managed in a primary tenant may be read-only elsewhere; make the change in that primary tenant. If the email address already exists, the application can offer an invitation instead. Transfer shared data, mailboxes, safes and responsibilities before deactivating or removing an account. The last administrator is protected.

Manage API keys

1. Open Management → API keys and start creating a key.
2. Enter a descriptive name for the integration and select its User. Both fields are required.
3. Set an appropriate Expiration date and check Active status. Without an expiration date, the key does not expire automatically.
4. Save and store the key securely. Test the integration on the correct product and tenant host with a read request.
5. To revoke access, edit the key and deactivate it, or delete it after checking dependent integrations. To rotate it, first create a replacement, update the integration and then deactivate the old key.

An expired key is inactive. Access depends on the selected user and their permissions; this form does not offer individual API permission scopes. Choose an appropriate user. The API guide explains the supported integration contract.

Check change history

1. Open Management → History.
2. Search for a relevant term and sort the table, for example by date.
3. Check the person, action and time. Browse subsequent pages if the entry is not visible.

History helps trace changes; it does not undo them.

Manage settings

1. Open Management → Settings.
2. Choose the relevant section. Available options depend on the product and enabled modules.
3. Record the previous value before changing it. Edit related fields together and check validation messages.
4. Save and open the affected feature using a regular user account. Verify that the intended change took effect.

Result

Users can sign in to the intended workspace, technical access has been checked and updated settings work as expected.

Troubleshooting

Related tasks

• Roles and permissions
• Password safe
• Troubleshooting