Just a moment...
Frequently asked questions about enterprise deployments.
The SPRL Enterprise FAQs provide answers to common questions about Enterprise planning, onboarding, user access, custom domains, platform usage, APIs, security, migration, support, and ongoing management.
These questions are intended to help organizations understand how SPRL can be incorporated into their existing business processes and what to consider when managing an Enterprise environment.
SPRL Enterprise is intended for organizations with broader platform requirements, including multiple users, brands, custom domains, campaigns, integrations, higher usage, or more complex operational workflows.
Organizations managing multiple brands or business units, higher link or traffic volumes, multiple campaigns, custom domains, API integrations, or multiple SPRL solutions may benefit from an Enterprise setup.
No. SPRL currently provides unlimited user login access. Organizations can provide access to their authorized users without planning around a fixed user-seat limit.
Not necessarily. The number of users alone does not determine whether an Enterprise setup is appropriate. Organizations should also consider their domains, usage, campaigns, integrations, security requirements, and operational needs.
Start by identifying your organization structure, user access requirements, custom domains, expected link and traffic volume, required SPRL solutions, API integrations, security requirements, and future growth.
Enterprise onboarding generally involves planning your requirements, configuring the platform and custom domains, setting up required services, integrating APIs, testing workflows, and moving approved processes into production.
The time required depends on the complexity of your organization's requirements, including the number of domains, integrations, products, campaigns, and workflows being configured.
Yes. Organizations can begin with a controlled set of domains, links, campaigns, or integrations, validate the setup, and expand their usage as their requirements grow.
Yes. Organizations can use SPRL across multiple departments and business functions while establishing their own internal processes for managing users, responsibilities, domains, campaigns, and other resources.
Organizations should identify authorized users, establish administrative responsibilities, review access periodically, and remove access when it is no longer required.
No. Individual user access should be used where available rather than sharing credentials between users. This makes access management and accountability easier.
Organizations should clearly define who is responsible for administration, custom domains, campaigns, API integrations, analytics, and other important platform resources.
Yes. Multiple custom domains can be configured and managed according to your organization's requirements and applicable account limits.
Yes. Organizations can use different custom domains or subdomains for separate brands, business units, campaigns, or other operational requirements.
Yes. Custom domains require the applicable DNS configuration before domain verification can be completed.
Yes. SSL activation is handled as part of the custom domain setup process after successful domain verification.
Review the DNS configuration, domain verification status, SSL status, and applicable troubleshooting documentation. If the issue continues, provide the affected domain and relevant error information when contacting support.
Yes. SPRL provides API capabilities that can be used to connect supported SPRL functionality with websites, applications, internal systems, and automated business workflows.
Supported API capabilities can be used for tasks such as automated short-link creation and other available platform operations.
API credentials should be treated as sensitive information and stored securely in your server-side or trusted application environment.
Private API credentials should not be exposed through browser-side code or other publicly accessible locations.
Secure the affected integration immediately and replace or deactivate the exposed credential where applicable. Review your application for unauthorized activity and take appropriate corrective action.
Yes. Existing links can be imported using the available file upload functionality in SPRL.
SPRL currently does not provide a direct automatic migration tool from another URL-shortening platform. Migration is performed by exporting your existing link data, preparing the file, and uploading it to SPRL.
Yes. SPRL provides bulk upload functionality for importing multiple links from a prepared file.
Yes. You can configure the relevant custom domain in SPRL and use it for imported links after completing the required DNS configuration, domain verification, and SSL activation.
No. Keep your existing platform active until your imported links, custom domains, and important production workflows have been successfully tested.
SPRL applies security-focused practices across areas such as application security, infrastructure, access management, secure communication, monitoring, abuse prevention, and operational processes.
Yes. SPRL uses HTTPS and TLS-based secure communication to protect information transmitted between users and supported SPRL services.
Yes. SPRL provides a Data Processing Agreement for Enterprise customers where applicable.
Visit the SPRL Trust Center and review the Security Policy, Privacy Policy, Data Processing Agreement, Acceptable Use Policy, Abuse Reporting Policy, and other applicable trust resources.
Potential security vulnerabilities should be reported through the responsible disclosure process described in the SPRL Security Policy.
For general platform assistance, account questions, and troubleshooting, use the SPRL Contact Us page to submit your request.
Provide the affected URL, domain, account or resource information, exact error message, expected behavior, actual behavior, reproduction steps, and relevant screenshots or technical details where applicable.
No. Never include passwords, API keys, access tokens, or other private credentials in a support request.
Use the SPRL Abuse Reporting process to submit suspicious or abusive links for review.
Large organizations should establish clear administrative responsibilities, consistent naming conventions, domain management practices, campaign processes, API management procedures, security controls, and internal documentation.
Review your environment periodically and whenever significant organizational changes occur. Pay particular attention to user access, custom domains, integrations, campaigns, security requirements, and important configurations.
Yes. Maintaining internal documentation for domains, integrations, responsibilities, campaigns, and important configurations can make ongoing management easier.
Consider future requirements such as additional users, brands, custom domains, campaigns, traffic, integrations, and business workflows when establishing your initial operating processes.
| Area | Recommended Practice |
|---|---|
| Users | Provide access to authorized users and review access periodically. |
| Responsibilities | Clearly define ownership of important platform resources. |
| Domains | Document and regularly review custom domains. |
| Campaigns | Use consistent naming, tracking, and management practices. |
| APIs | Protect credentials and maintain reliable integrations. |
| Analytics | Monitor relevant traffic and campaign performance. |
| Security | Protect credentials, review access, and follow applicable security policies. |
| Documentation | Maintain records of important configurations and workflows. |
| Topic | Summary |
|---|---|
| User Access | Unlimited user login access is available. |
| Onboarding | Plan, configure, integrate, test, and launch your Enterprise environment. |
| Custom Domains | Multiple domains can be configured according to your requirements and applicable limits. |
| API | Supported SPRL functionality can be integrated with applications and workflows. |
| Migration | Existing links can be imported through file-based bulk upload. |
| Security | Review SPRL security, privacy, data processing, and acceptable use resources. |
| Support | Use the Contact Us page for platform assistance and troubleshooting. |
| Growth | Establish processes that can adapt as your organization's requirements expand. |
Our support team is always happy to assist you.
We use cookies to improve your experience, analyse traffic, and personalise content. By clicking “Accept”, you consent to the use of cookies as described in our Cookie Policy .
Accept cookies Read our Cookie Policy
