Administration and governance

Administrators can manage users, links, global feature availability, user-specific overrides, advertising visibility, abuse limits, login and registration protection, email settings, link health settings, commercial access, and operational defaults. The goal of the admin area is to let the site owner adapt clk.ms to policy, risk, workload, and business needs without changing how ordinary users create and manage their links.

Administration controls help the site owner manage policy, risk, and operational defaults. Admins can manage users, links, feature availability, user-specific overrides, advertising visibility, abuse thresholds, login and registration protection, email settings, link health settings, commercial access, and other global behavior. The goal is to adapt clk.ms to business rules without making ordinary users learn administrative details.

Global settings are useful when a policy should apply to everyone. User-specific settings are useful when a trusted customer, internal employee, or partner needs a different limit or feature set. Advertising controls, cache sizes, abuse windows, and email settings can be adjusted as the site grows or as operational needs change.

Example: an admin can enable QR features for registered users, disable advertising blocks for a paid plan, increase allowed public creation limits for a trusted partner, and permanently block an IP address that created malicious links.

Best practice: change global settings carefully and document why they changed. Prefer user-specific overrides when only one account needs different behavior. Review abuse and registration settings after real traffic patterns appear.

How to apply this section

Each topic explains a feature, the user decision behind it, and how to use it without making the link harder to manage. Read the checklist before changing a link that is already shared.

Before you publish or update

Start from the visitor experience: who opens the link, from where, on which device, and what should happen next.
Check that the destination is correct, opens quickly, and shows the expected page for the intended audience.
Choose only the controls that match the goal, such as expiration, password, referrer, QR design, UTM, routing, or analytics sharing.
Save a short note for important changes so future review, rollback, or teamwork stays clear.
Open the short link in a private browser session and, when relevant, test mobile, desktop, QR scan, and protected access paths.
Review analytics after sharing to confirm real visitors, source quality, device mix, and campaign performance.

Practical example

Example: create a test link for an internal page, add a clear slug, set a short expiration, enable preview if the destination is sensitive, scan the QR code from a phone, then check whether the visit appears in the link statistics.

Next step

After this topic is clear, combine it with one adjacent feature. For example, pair UTM with campaigns, QR with print layouts, targeting with fallback, or webhooks with conversion tracking.