Hi @NidhiRaj ,
Thanks also for the information.
-
I second Marc’s question about the user-picker and potential security issues. As part of this, I understand that you have planned to supply a context parameter indicating whether the current user is an external collaborator or not. This parameter is partially helpful, but this information also needs to be surfaced in the correct domain (the user object). Some apps may be doing maintenance tasks on separate threads, handling webhooks, or otherwise manipulating user data and needing to decide how to treat a user outside of a web context. How soon can this be done, so that when we fetch a user object via API, we get the external collaborator status? And how can apps retrieve the ID or key of the single space to which the user has access?
-
Introducing the concept of partial functional access to Confluence for a subset of users raises a set of concerns, and it’s a bit of a slight of hand to say that apps can truly “opt out” of this feature. For example, if a Confluence app provides a macro, what would it even mean to “opt out”? The idea of “External collaborators can’t create new instances of macros” is one interpretation, but there will also be apps whose resources are consumed just by viewing macros. And even the first interpretation of preventing creation could be tricky (Can external collaborators edit existing macros? What happens if they edit a page containing one?).
-
Can you confirm that external collaborators are prohibited from having personal spaces?
-
This is described as a four-month beta, but per the rollout schedule on the partner portal, this is actually rolling out live for all paid sites soon. This feature is apparently already live today for some customers, so providing limited information like “Detailed information on what a guest can and can’t do to follow” is really far from ideal. What significance does “beta” have in this context, when it is rolling out to everyone? It seems like Marketplace partners should have had much more advance notice of this entire feature, and also have had an Atlassian involved in the design process who could act as a champion for Marketplace vendors.
Scott