Configure Your Palladium AI Team Workspace Settings

Configure your Palladium AI workspace: set team identity, structure multi-branch navigation, and control access before onboarding members.

Before you invite members and start recording financial activity, take a few minutes to configure your workspace correctly. Getting your team identity, branch structure, and access control right at the start means less rework later and a cleaner experience for everyone on your team. This guide covers the key configuration steps and points you toward more detailed references for each area.

Team identity

Your team’s name is the primary label that appears across your workspace — in the navigation header, in reports, and in any exports you generate. Choose a name that matches your organisation’s official identity so that members and admins recognise it immediately.

When you create a team, Palladium AI generates a team slug — a short, URL-safe identifier derived from your team name. This slug is embedded in your workspace URLs, making each team’s links uniquely addressable and stable.

The team slug is set at creation time. If you need to rename your team’s display name later you can do so in team settings, but the slug is fixed to maintain stable links and integrations.

Multi-branch setup

If your organisation operates multiple branches or chapters, the recommended approach is to create a separate team for each branch. This keeps financial records, member lists, and settings cleanly partitioned — an admin at one branch cannot accidentally view or edit records belonging to another.

You are not limited to one team per account. After creating your first team, use the New Team option in the team selector to add additional teams for other branches. Once you have multiple teams, you can move between them instantly using the team selector in the navigation sidebar — no sign-out required.

For organisations that need a consolidated view across all branches, the platform owner role provides cross-team visibility without disrupting branch-level isolation.

Access control overview

Every user in a Palladium AI workspace is assigned one of three roles:

Role	Description
Member	Day-to-day access to savings, loans, and member record views within the team
Admin	All member permissions, plus the ability to manage workspace settings, invite users, and configure roles
Platform owner	Highest level of access; designed for centralised oversight across multiple teams in a network

Assign roles thoughtfully when you invite people. You can update a user’s role at any time from the Members management area. For a full breakdown of what each role can and cannot do, see the Roles & Permissions reference.

What to configure next

With your team identity set and your branch structure in place, you are ready to complete the remaining setup tasks. Work through these in order to have a fully operational workspace.

Invite Members

Add your colleagues and staff to the workspace by sending email invitations from the Members panel.

Set Roles

Review the full permissions matrix and assign the right role to each user in your team.

Set Up Savings

Configure your savings workspace and record your first member deposit.

Set Up Loans

Prepare your loan pipeline and submit your first loan application for review.