Overview

Managing a large organization on SPRL involves establishing a clear structure for users, responsibilities, domains, campaigns, integrations, and other platform resources.

SPRL provides unlimited user login access, allowing organizations to provide access to their authorized users without having to manage a fixed number of user seats. As your organization grows, maintaining clear responsibilities and consistent operating practices becomes increasingly important.

Organization Structure

Before expanding SPRL usage across a large organization, define how different departments, business functions, brands, and campaigns will use the platform.

A clear structure makes it easier to manage resources and maintain consistency as more users and business functions begin using SPRL.

• Identify the primary organization administrators.
• Define responsibilities for different business functions.
• Document which teams manage specific campaigns or domains.
• Establish internal processes for managing platform resources.
• Keep documentation for important configurations and workflows.

User Access Management

SPRL provides unlimited user login access. Organizations can therefore provide access to the users who require it without having to purchase individual user seats.

For large organizations, the focus should be on ensuring that users have appropriate access to the resources and responsibilities relevant to their work.

• Identify users who require platform access.
• Maintain an internal record of authorized users.
• Assign administrative responsibilities clearly.
• Review access when employees or responsibilities change.
• Remove access for users who no longer require it.

Managing Multiple Domains

Large organizations may manage multiple brands, products, departments, regions, or campaigns. Custom domains can help maintain separate branded link experiences for these different business requirements.

Maintain an internal record of connected domains, their intended purpose, and the team or business function responsible for each domain.

Managing Campaigns

Large organizations may run multiple campaigns simultaneously across different channels and business units.

A consistent campaign management process helps prevent configuration errors and makes analytics easier to interpret.

• Use consistent campaign naming conventions.
• Organize links according to campaigns or business functions.
• Use appropriate branded domains for different campaigns.
• Verify destination URLs before launching campaigns.
• Monitor campaign analytics after launch.
• Document important campaign configurations.

Resource Management

As the number of links, domains, campaigns, forms, and integrations increases, organizations should establish a consistent method for managing their platform resources.

Administration Responsibilities

Large organizations should clearly define who is responsible for maintaining the SPRL environment.

• Account and organization administration.
• User access management.
• Custom domain configuration.
• API integrations.
• Campaign management.
• Analytics and reporting.
• Security and compliance coordination.

Analytics & Reporting

Large organizations can generate significant amounts of link and campaign activity. Establishing consistent reporting practices helps teams understand performance across campaigns, domains, and business functions.

• Define the key metrics your organization needs to monitor.
• Use consistent campaign naming and tracking conventions.
• Review traffic and click activity regularly.
• Compare campaign performance across business functions.
• Use analytics to identify trends and optimize campaigns.

API & Integration Management

Organizations with multiple applications or automated workflows should maintain clear documentation for their SPRL integrations.

• Document each application connected to SPRL.
• Record the purpose of each integration.
• Keep API credentials securely stored.
• Review integrations periodically.
• Monitor integration errors and unexpected activity.
• Deactivate credentials that are no longer required.

Security & Privacy Management

Organizations should incorporate SPRL's security and privacy requirements into their internal operational processes.

• Review the SPRL Security Policy.
• Review the Privacy Policy.
• Review the Data Processing Agreement where applicable.
• Follow the Acceptable Use Policy.
• Review API security requirements.
• Maintain appropriate internal access controls.
• Periodically review users and integrations.

Operational Best Practices

• Maintain consistent naming conventions.
• Document important platform configurations.
• Review user access periodically.
• Keep domain information up to date.
• Review active campaigns regularly.
• Monitor API integrations and credentials.
• Maintain internal ownership for important resources.
• Test major configuration changes before production use.
• Review analytics and platform activity regularly.

Managing Organizational Changes

Large organizations frequently change teams, responsibilities, brands, campaigns, and business processes. Review your SPRL environment whenever significant organizational changes occur.

When responsibilities change, review the users, domains, integrations, campaigns, and other resources associated with the affected business function.

• Review affected user access.
• Update administrative responsibilities.
• Review associated custom domains.
• Review API integrations.
• Update campaign ownership and documentation.
• Remove access or credentials that are no longer required.

Large Organization Checklist

Frequently Asked Questions

Does SPRL limit the number of users in a large organization?

No. SPRL currently provides unlimited user login access. Organizations can provide access to their authorized users without a fixed user-seat limit.

How should a large organization manage users?

Organizations should establish clear internal responsibilities, periodically review access, and ensure that users only retain access that is required for their role or responsibilities.

Can multiple departments use the same SPRL environment?

Yes. Organizations can use SPRL across different departments and business functions while establishing their own internal processes for managing resources and responsibilities.

Can large organizations manage multiple custom domains?

Yes. Multiple custom domains can be configured and managed according to the organization's requirements and applicable account limits.

Should different teams use different domains?

This depends on your organization's branding and operational requirements. Separate domains or subdomains can be useful when different brands, business units, or campaigns require distinct branded link experiences.

How should API integrations be managed?

Maintain documentation for each integration, keep API credentials secure, review integrations periodically, and remove credentials that are no longer required.

Quick Reference