This idea has been archived, contributions have been disabled 

Comments (9)

Karolina Jackson-Ward
Karolina Jackson-Ward

Karolina Jackson-Ward

Level
0
Score
41
Team

Interesting! We had a customer writing in with the opposite opinion a while ago:

http://ideas.projectplace.com/feedbacks/225488-copy-folde...

I agree that we could communicate better the difference between copy and cut.

When you copy a folder, a new folder is created that has a copy of the contents of the old one, The history and other attributes, like access rights, however, are the same as if you had created a new folder. They stay with the original.

When you cut and paste a folder, you just move it. All the history and access rights are still there.

So Ulrica, your problem could be solved by creating a copy of the folder (and then possibly deleting the original) in the new location.

Let us know what you think would be the best solution to this:)

Ray Smith
Ray Smith

Ray Smith

Level
0
Score
16

The problem with this solution is you then loose all the meta data that was on the original document. I am guessing that the audit trail (History) is pretty important to keep.

Karolina Jackson-Ward
Karolina Jackson-Ward

Karolina Jackson-Ward

Level
0
Score
41
Team

Absolutely...and we can't keep the history when you copy...because then you would have multiple documents with the same history...which I guess wouldn't make much sense.

Hi
See Aage Heir's suggestion "Better user/group admin" and my comments to his suggestion for a "Road Map" attached to all access control on all 3 levels in PP enabling you to see /get ann logical overview of different settings.
Suggest you also vote for that suggestion

Thorolf Huus

The top ideas with status Quality Backlog are discussed on a regular basis with the design team. These should be minor development, and could include hygiene factors, little things that create a wow effect and ideas that could have a positive effect on a lot of users.

Mette B-P
Mette B-P

Mette B-P

Level
0
Score
0

Hi all,

I think both suggestions are valid because it is all about what the user expects. From my point of view security is one of the most important things which is partly why I chose to use ProjectPlace in the first place (server side encryption, backup etc.). It is of vital importance that we can trust, that users do not see information that we do not want them to see. So handling security on documents, tasks, issues etc. in all types of scenarios is very important. Otherwise I cannot use ProjectPlace for my important projects. For me it is that simple.

I find ProjectPlace to be really useful and providing functionalities that I have not found in my other collaboration tools. I just wish that ProjectPlace would also excel on functional security.

Thanks.

Hi all,

We are doing a pre-study for a better overview and a better way to set access rights in Projectplace. No new functionality is included in the scope of the project but we want to make the existing functionality easier to use. If you want to help, we would be grateful to know in which situations you are when you find the current solution frustrating. What do you think could improve it?

DIMELO - SocialCRM software editor