Team Management Policy

LeadForge organizes team collaboration through Workspaces while also supporting Personal data and workflows for individual users.

A Workspace may contain shared leads, territories, activity, imports, tasks, Pitch Deck references, collaboration, analytics, and other records made available to users according to their permissions.

Not every LeadForge record is automatically a Workspace record. Some information remains Personal to a user even when that user also belongs to a Workspace.

LeadForge uses Personal and Workspace data scopes to control which records a user is viewing and which records may be used by supported features.

Personal scope is intended for records and activity associated with the individual user. Workspace scope is intended for records shared or made available through the Workspace.

A user may have access to one scope, both scopes, or different capabilities in each scope depending on plan, role, and permissions.

Changing the visible scope does not transfer ownership of a record or grant access the user did not already have.

LeadForge may distinguish Workspace owners, administrators, members, and other product roles or access states.

Owners and administrators may have authority to manage membership, grant or revoke Workspace access, configure Workspace settings, manage capacity, and perform other administrative actions exposed by the product.

Members may have narrower rights and may be permitted to view or use shared Workspace information without having authority to delete, reassign, configure, or administer all Workspace records.

Role labels do not override feature-specific ownership, consent, privacy, or authorization rules.

A user must be authorized to access Workspace-scoped information. LeadForge may expose Personal and Workspace selectors even where one option is unavailable to the user so the product can clearly communicate the applicable access boundary.

Granting Workspace access may make Workspace-scoped records available to the user and may enable Workspace-aware AI context or collaboration features.

Revoking Workspace access removes the user’s authority to access Workspace-scoped records but does not automatically delete records that belong to the Workspace or other users.

Subscription plans may include a defined number of seats or team-capacity allowances.

LeadForge may prevent invitations or additions that would exceed available capacity and may offer additional seat or team-capacity purchases for eligible paid plans.

Seat capacity determines whether another eligible user can be added; it does not by itself determine that user’s role, Personal or Workspace access, ownership rights, or permissions.

Workspace owners or authorized administrators may invite eligible users to join a Workspace subject to seat capacity and the invitation rules enforced by LeadForge.

An invitation may expire, be replaced, revoked, or otherwise cease to be actionable according to the product’s current invitation lifecycle.

Users should accept invitations only for Workspaces they are authorized to join. Workspace administrators are responsible for removing users whose access is no longer appropriate.

Records created or designated as Workspace-scoped may remain available to the Workspace even if the individual user who created or contributed to them later leaves or loses access.

Examples may include Workspace activity, shared leads, Workspace Lead Intelligence, meeting artifacts, shared task results, imports, Team Threads, Workspace analytics, and other records whose product scope is Workspace rather than Personal.

The exact deletion and ownership effect of a product action depends on the record type and the control used. Removing a user or deleting a visible card does not necessarily delete every underlying source or audit record.

Personal records remain associated with the individual user unless a product workflow expressly transfers, shares, or creates a separate Workspace representation.

Personal and Workspace versions of similar artifacts may coexist. A Workspace representation does not necessarily give the Workspace ownership of the user’s editable Personal version.

Where LeadForge provides Workspace views of generated material, the Workspace copy may be read-only, canonical, or independently maintained according to the product’s current design.

Workspace users may be permitted to view leads owned or created by other Workspace participants when Workspace access and feature rules allow it.

Viewing another user’s lead does not automatically grant authority to remove it, mutate its Personal state, or take ownership of the record.

Lead Intelligence may have Personal and Workspace visibility or provenance rules distinct from the underlying lead record.

Business Partner Tasks may be scoped to a lead, territory, Workspace, or other supported target. The targets visible to a user depend on the user’s access and the selected data scope.

Task Results and other generated work may be Personal or Workspace-scoped. Users without Workspace access should not be given Workspace-only targets or results merely because another feature can see them.

Pitch Decks and other generated materials may have separate editable Personal ownership and Workspace read-only or canonical representations.

LeadForge provides Team Threads, group conversations, direct messages, and shared-work references for collaboration.

Some direct-message functionality may allow users to communicate across Workspaces when they know another user’s supported identity or username. Cross-Workspace messaging does not grant access to the other user’s Workspace data.

Closing a direct-message view for one participant does not necessarily delete the other participant’s retained conversation history. Shared-work links remain subject to the recipient’s authorization when opened.

Where a user has Workspace access, LeadForge Copilot and other AI-assisted features may use Workspace context according to the selected mode, feature, permissions, and available records.

Personal and Workspace AI context are intentionally separated so that users without Workspace access are not given Workspace-only information.

Workspace owners and administrators should grant access carefully because expanded Workspace access may also expand the information available to Workspace-aware AI features.

Certain subscription capacity, such as Discoveries, AI usage, seats, or other plan entitlements, may be shared at the Workspace level even when the action is initiated from a Personal product view.

Lead unlocks are free and are not a shared paid unlock-credit pool.

The Billing & Usage Policy governs how usage is associated with users, Workspaces, subscriptions, and add-on capacity.

Workspace owners and administrators are responsible for managing membership, granting and revoking Workspace access, reviewing capacity, protecting administrative accounts, and configuring Workspace features appropriately.

Administrative users should not assume that their role permits them to override participant recording consent, another user’s Personal ownership, connected-service authorization, or other feature-specific legal requirements.

LeadForge may restrict administrative actions where needed to preserve security, ownership, billing integrity, or legal compliance.

When a user leaves or is removed from a Workspace, the user may lose access to Workspace-scoped records while retaining Personal records that remain associated with their account.

Workspace records do not automatically become Personal records when access ends, and Personal records do not automatically transfer to the Workspace merely because the user was once a member.

Historical activity, messages, shared artifacts, audit records, billing records, and other records may remain as described in the Data Retention & Deletion Policy.

Workspace administrators should invite only authorized users, remove inactive or unauthorized users, protect administrative access, review connected services, and report suspicious activity.

Users must not attempt to access another Workspace, scope, lead, artifact, message, or administrative function beyond the permissions granted to their account.

LeadForge may update Workspace roles, access models, collaboration features, seat rules, Personal and Workspace scope, or team-management functionality as the Service evolves. The current version will be published in the Legal & Trust Center.