> ## Documentation Index > Fetch the complete documentation index at: https://docs.landerlab.io/llms.txt > Use this file to discover all available pages before exploring further. # Team and Workspaces in LanderLab: Overview > Learn how to organize LanderLab for a team: workspaces for clients and brands, user roles and access control, AI credit limits, and system activity logs. LanderLab is structured in two layers. Your **organization** owns billing, users, and saved integrations. Inside it, **workspaces** hold landing pages, domains, and access permissions. Getting that structure right early saves a painful reorganization later, once you have two hundred pages spread across the wrong containers. ## Workspaces A workspace is a container for landing pages, domains, and team access. How you divide them depends on how you work: * **Agencies** create one workspace per client, so a client's team can be given access to their own pages and nothing else * **In-house teams** usually split by brand, vertical, or region * **Solo operators** often need only one, and should not overthink it Create workspaces, rename them, and understand what is shared at the organization level. Pages are not stuck where you first created them. [Move landing pages between workspaces](/features/landing-pages/operations/move-to-workspace) when a client or project changes hands. Integrations are saved at the **organization** level, so a CRM connection added in one workspace is available in the others. Landing pages and domains belong to their workspace. ## Users and roles Adding people to your organization and assigning them a role controls what they can see and change. Access is granted per workspace, which is what makes the client separation above meaningful rather than cosmetic. Invite team members, assign roles, and control which workspaces each person can reach. Give people the narrowest access that lets them do their job. A copywriter editing one client's pages does not need visibility into every other client's leads. ## AI credit limits AI generation consumes credits, and credits are shared across your organization. Without limits, one person experimenting with page generation can spend a month's allocation in an afternoon. [Credit limits](/features/multi-user/credit-limits) let you set a monthly cap per team member and monitor usage across the organization, so you can distribute AI access without handing out an unlimited budget. ## Activity logs Track every change made across your organization. Filter by user, category, or date range and open the full detail of any event. Logs answer the question that comes up on every team eventually: who changed this, and when. They are also the fastest way to diagnose a page that stopped converting overnight, since a configuration change usually shows up right before the drop. ## A structure that scales If you are setting this up for the first time, a reasonable default: Keep the boundary at the level where access needs to be separated. Group by campaign or funnel using [folders](/features/landing-pages/folders/create), not by adding more workspaces. Add people to the workspaces they work in and nowhere else. Set caps when you add someone, not after an unexpected bill. ## Where to go next