Keep dev, staging and production links in one team library

Choose a home your team will actually maintain

For a handful of links used in one Slack channel, that channel may be enough. Slack supports links inside tab folders; see its official guide to managing tabs.

A document is a good fit when the main content is setup instructions, troubleshooting or a runbook. Keeping those explanations and their URLs together can make updates simpler.

A dedicated link library becomes useful when people open links every day across several products and need to browse by environment or purpose. Whichever tool you choose, agree on one maintained source rather than creating a new list in every chat thread.

Make the destination clear before the click

Here is an example for a fictional product called Atlas. These are naming examples, not live development environments.

An address such as https://stg.example.com is suitable for an illustrative example. Replace it with a verified address in your actual workspace. A title of “Admin” alone leaves too much to guess; include the product and environment in the title itself.

Use collections for products and tags for environments or functions. This is a naming convention you apply, not automatic environment detection by linqlo.

Build and check the shared library in five steps

1. Check seats and the Team plan

Team costs US$7 per person per month, with a minimum of two seats. That makes the base price for two seats US$14 per month; check the pricing and checkout screens for the applicable payment terms. Personal Free and Pro are not free collaborative team plans.

2. Select a team workspace

After registering and signing in, choose the team's workspace from the workspace switcher or use “Create workspace” to make one. Creating a workspace does not activate Team by itself. Check its subscription in settings under the plan and billing section before inviting members.

3. Add one product's essential links

Create a collection and add the dev, staging, production and admin URLs you actually use. Use “Detailed entry,” or edit after saving, to set the title, “Save to,” tags and memo. If the destination is a login screen and its retrieved title is unhelpful, replace it with your agreed name.

4. Invite a colleague and verify their view

An owner or admin can open “Settings” → “Members” and use “Invite a member” to enter an email address and role. The recipient accepts the invitation and opens the team workspace. Check that they can find the same collection and links; sending the invitation alone does not verify their access.

5. Assign responsibility for changes

Agree who updates a URL when an environment changes. For example, the product's maintainer can update links during a change and review the list before a release or handoff. Use memos for purpose and a contact point. Writing a maintainer's name in a memo is a team convention, not a built-in assignment workflow.

A link is not an access permission

Joining the linqlo workspace does not create an account in the destination application or grant its admin role. VPN, SSO and application permissions still need to be arranged separately. Keep passwords and API keys in your team's credential management system rather than embedding them in bookmark URLs or notes.

Workspace collaboration is also separate from public collection sharing. You do not need to enable “Share publicly” to use an internal link library with members. A publicly shared link is not a replacement for internal access controls.

Questions about team URL management

Can I invite a team for free?

Collaborative use is part of Team, starting at two seats. Being able to create a workspace does not mean extra members are included in a free plan. Check the cost for the people who will join.

Is there a template that creates every environment automatically?

This guide uses existing collections, tags, titles and memos. Build the example manually and adapt it to your product. It does not assume one-click template duplication or automatic detection of dev, staging and production URLs.

Can I hide personal links inside the shared workspace?

Use a separate personal workspace for personal links. Do not assume that a bookmark or memo in the team workspace has a per-item private mode. Add information intended for that team.

What should we check when a saved URL does not open?

First confirm the product and environment, then check the destination's login and VPN requirements. If the address changed, ask the library's maintainer to update it. A visible bookmark does not prove the destination service is currently healthy.