Users with View-Only permissions in a location cannot copy the internal link to a task. This makes it difficult for them to share tasks internally through other communication channels (e.g., Slack, Teams, or verbal updates). Without this ability, teams rely too heavily on tagging in comments or email notifications, which often get ignored or dismissed. The lack of link-sharing capabilities causes bottlenecks, stalls workflows, and reduces visibility into tasks that need follow-up.
Current Limitations
- No Link Copying for View-Only Users: View-Only users cannot copy task links even when they have visibility of the task.
- Over-Reliance on Notifications: Teams must tag users in comments or generate email alerts, leading to notification overload.
- Workflow Bottlenecks: When email notifications are dismissed or ignored, tasks lose visibility and stall.
General Example
A View-Only user identifies a task requiring follow-up by another team. Because they cannot copy the internal task link, they tag a colleague in the comments instead. The notification goes to the colleague’s email, but it is overlooked in a crowded inbox. As a result, the task is delayed because there is no quick, reliable way to share the direct link internally.
Requested Enhancements
- Enable “Copy Link” for View-Only Users
Allow View-Only users to copy internal task links while preserving their view-only permissions. - Permission-Safe Implementation
Ensure View-Only users cannot make edits but can still share task links internally. - Better Collaboration Support
Make it easier to share links via company communication tools without spamming comments or emails.
Business Value
- Workflow Continuity: Keeps tasks moving by making it easier to share them across teams.
- Reduced Noise: Cuts down on unnecessary emails and repeated notifications.
- Collaboration: Enables teams to coordinate outside of Limble without losing context.
- Efficiency: Ensures the right people can access the exact task quickly, even if shared by a View-Only user.
