I have a couple of questions…
1) When you set the “Shared as” = View, can other read the view-only version, but save a new version? Or would they only have the option to save a new document?

2) With the View access, could anyone then relate the two documents? Or would you require Public or ACL=Full Access for that?

Thanks!

1. What about security (and metadata) on documents that are in multiple locations? Whichever folder or WorkSpace that is refiled last will set the “winning” values, which may not be correct.

2. Client-side or desktop refiling is certainly inefficient (every document is touched and changed, even if no changes are actually performed) and can be inherently dangerous (users with adequate security rights can damage the security and metadata of potentially many documents if they are not careful which options they choose in the refiling process, or they make changes but select “No” on the refiling dialog and not actually implement the changes). Users who refile a WorkSpace and tie up their machine for several minutes may decide not to do that again in the future…

3. No history events are added to documents during the native refiling process, so refiling causes untracked changes to document profiles.

Our Refiling Server products address all of these issues, and many more, such as providing control over which metadata values can be changed as part of the refiling process, how documents in multiple locations are handled, and providing history logging of changes. They completely eliminate all client- or user-side refiling, and allow for much faster and efficient server-side refiling.

Also, what are the implications of user ACLs on structures in terms of what abilities they have to create or modify structures within WorkSpaces? Again, the Zone Control functionality of our WorkSpace Manager product allows control over which users or groups can create ad hoc structures, completely independent of their security rights.