I wish there was a way that I could share the XD app view experience (view only). Currently, if I share the XD file with a stakeholder and they have XD on their desktop, they can open, edit, etc. I want them to only see the it though the XD mobile app. I know I can send them the weblink but that comes with browser bar, etc.

For a design team, it is necessary to be able to give a fellow designer access to view and copy from file without giving them ability to edit stuff on your file.

A read-only view for devs is a must. I've shared the developer view before, but then you lose everything that's not in an artboard, which loses a lot of context.

I have been running into a ton of issues where I have invited my devs to edit the file. If they open the file while I'm in it, and haven't saved, I'm forced to "accept remote changes". I want to be able to give devs access to just view or exports assets, not move any design elements.

Same here: I want to provide a read-only stcker sheet for internal and external colleagues and prevent them form accidentally change stuff. Sharing published libraries is very handy but does not replace ticker sheets that provides an overview of all elements on the screen including annotations.

I share master documents as guides with the rest of the team. I want them to be able to use them as reference and copy elements/artboards from them along with the library file. However I do not want them to be able to edit the master file. There doesn't seem to be an option for this? Which means I have to accept peoples changes whether I want them or not. How frustrating!

A SINGLE DOCUMENT for Primary users create, managing, modify assets and Secondary users to have access but are only limited to read rights.

This would be a huge step forward for our team as we try to share XD files across larger and larger groups of designers.

We need a way to maintain a source of truth and make it available for use internally, without granting edit access to every user of the file.

I would echo the comments of Brad, Jason, and Will.

The most important aspect for me is the inclusion of different roles to enable to core design system team to communicate the design system to distributed project teams.

Those designers on project teams should be able to grab assets but not make changes to the design system file.

The proposal by Jason is pretty clear and would go a long way to make XD a viable choice for large organizations and governments.

adobe xd is already awesome software but i would like to tell you that some few points should need to add too, for example: we have an option to secure our file or artboard, we should have option for lock artboard (full artboard not just elements) and not editable now you will think if i don't wanna share my work then i should share link of my work so i wanna tell you that sometimes we need to share xd file but we don't want that anyone could edit something, so we don't have any option for it.
you can add this feature easily that anyone else can not edit the file and if anyone want to edit the file he/she need to permit for access for it.
1) whenever he will click on artboard password popup will be display.
2) you can add more secure options you guys understand better than me :)
i hope you'll like my idea and positive reply will be waited.

Thanks,
Laique Ahmed

I need the ability to allow admin/ownership to be passed to another user. At the moment having the document owner be the only one who can grant access forces them to be a gatekeeper and not ideal.

I use CC Libraries as a work around because it allows read-only permissions but the XD components don't sync states and aren't linked so if I make a change to the original master my designers don't get the updates automatically (which XD assets does fantastic) but if I shared the file with them they could edit the masters which I don't want.

I want to grant permissions to the users whom I shared the file with.

In other words, I want to share a UI kit that contains a lot of well-designed UI components with my team to fast pace our work but I don't want them to edit the file. They can just view it and can make copies of the existed UI components.

I'm always worried my devs will forget to save a local copy and mess up the cloud file. Please allow for access rights by Creator when sharing or inviting people to file via the cloud.

This is typically big company basic features Adobe need to take into consideration if they want to be adopted

I worked at a large multinational corp. I must share the assets without allowing our numerous team members to edit them. As of now I don't share the assets via Adobe CC. I share it as a file on a Sharepoint sever. Huge thumbs down.

Ability to share files with view access only.
Example: share a UI/Brand library with other designers to use components/styles without letting them edit master file-like sketch or figma libraries.

We could consider a workaround with CC libraries. You import all your components in a CC library. Then you share it to the members of your team. With this approach you can set permissions (edit, read only). This way your team can work with the elements without breaking the consistency. BUT, doing so, if you want to update an element inside the library, you have to delete it and re-import the updated one.... Which of course have no impact on the existing files using the previous component -> pointless. A design system is not for designers only, please listen to all of these meaningful comments !

I would like to share with other users in read only mode so our Design System is only updated by the design team and the conception team can only import assets or open the file.

Is there a way to share an XD cloud document (design system) with someone and not grant them access to edit the document? Similar to CC Library sharing (view access only). That way they can link to the assets but are unable to edit the original assets.

We have 50+ designers that use our design system and if they all have edit access to the master document there will be chaos.

The fact that we can't easily revert changes only compounds this issue.