Another perspective: You might want to control who is able to read what you are sharing. If you allow everyone to view read only links you have no way of knowing when it is being accessed by others than for whom you intended this.
Any further update on this? I would like the public link to show exactly the same and all columns that a project has but obviously with read-only access. However, currently the link shows only a couple of columns and missing a few. Is there a way to fix this? Thanks.
1 Like
+1!! This is much needed.
1 Like
Whatâs the current status? This is desperately needed.
Is still a new feature??? Lol
This issue/feature request is almost 3 years old. Without word of movement on it, I can only assume Asana will not be adding it. We were looking to expand the level we use Asana, but will now be looking at other options. Such an easy feature to implement, itâs baffling why Asana wouldnât display custom fields in public, read-only views.
No word from Asana doesnât mean anything, knowing that they donât communicate on the roadmap. If they came every month saying ânot part of the roadmap yetâ you would be equally angry (or even angrier). Make sure to upvote at the top!
And if people can stop saying a feature Is âeasy to implementâ that would be great 
nothing is easy when your app is used by millions of people, on multiple devices, in multiple languages.
Food for thoughts: letâs say they do develop this feature. Letâs assume they turn it on one day. Then thousands of read-only views suddenly show information that used to be hidden. Well, ok, youâll tell me âletâs add a toggle to let people chooseâ and then you just made Asana codebase more complex, harder to explain etc
1 Like
This is a valid point. However, as it stands, the list of projects and dates already falls under this type of shared experience. What I think people are asking for (myself included) is the option to show a more customized set of information in this âno strings attachedâ format.
For example, if Iâm comfortable with someone viewing my tasks and due dates as you described, why wouldnât I also want to show a custom fieldâlike a production statusâthat conveys a key piece of information specific to the audienceâs needs?
If sharing information like task names and due dates is considered safe, then why is it seen as a higher risk to share additional fields, like production status, that might be just as valuable but less sensitive? It seems arbitrary to label some information as safe and other details as too risky when, in many cases, the custom fields would be just as useful without adding extra risk.
Because custom fields can contain things like time spent, time estimated, budget, cost, hourly rate⌠There is a wide range of risky fields people use, so to me it was a smart move to release the read-only feature without field and then work on the ability to pick the fields you want to show (instead of not releasing anything until everything is ready). We discuss this lean way of releasing features in đŚ If Wishes Were Unicorns: Why Asana Might Not Have Implemented that Feature Request (and other thoughts about Asana feature development and product strategy)
2 Likes
+1 from our org.
+1 from our org, we have lots of external partners who need visibility into status and prioritization custom fields. Right now, the view-only link is useless for this, and we are forced to export information into Google sheets, which then creates duplicate info to be managed.
2 Likes
Hey Team! Any updates on this topic?
I think a great thing to have is toggle on/off fields to show for a specific dashboard, or create a specific view with the hidden fields and make it shareable (we already have this ability for main tasks)
2 Likes