Setting theme_url_prefix in setup_themes(app, theme_url_prefix='/themes') does not appear to help.

Robert should not be able to just join Susy's editing session without either Susy or the owner of the deployment (and therefore arguably the owner of all files) having pre-approved this level of association of rights outside the session with implicit rights to join and/or manage access on such session.

Really, Eva migrating systems or systems' storage backends while already running Manticore and/or Chwala is currently so much a hypothetical scenario it really can't have the same priority as the other stories/tasks.

I need to add that Chwala will likely want to apply a type of lock that allows the file to be marked as being locked (in a collaborative editing session) in other UIs (webclient), rather than just "a lock". This lock could be of such type, amended with such identifier, as to establish the static URI for Manticore to speak to.

Should Manticore use Chwala as it's storage backend, Manticore would not be involved in fulfilling the requirements in this particular user story -- it would just speak to Chwala and leave the canonical location for the document origin to be the URI to Chwala.

In T723#10323, @Adityab wrote:

[1] The most convenient solution would be to have administrative rights available handy to work on a shared folder. If, however, only a system that exposes individual rights is possible, then enough exposure of who has what permissions on a source document is required.