Password protection for family "Edit Type"

January 22, 2013

Password protection for family “Edit Type”

Filed under: Families — harrymattison @ 2:09 pm

A reader asked if it was possible to require a password before allowing users to push the Edit Type button. Is this of interest to others?

About these ads

Comments (13)

13 Comments »

Harry
This is the Best API yet

Thank you
Marcello

Comment by M S — January 22, 2013 @ 2:10 pm

Reply
definitly!

thanks!

Comment by David — January 22, 2013 @ 2:22 pm

Reply
Hello Harry
it could help for some families (type catalog driven for ex.). but won’t for some others. Could be usefull to do the same for the f* double click editing or editing the family. but could it be stored in the rfa file?

thanks again for this cool blog. Macro about CAD import is part of my template file now. Awesome!

Julien

Comment by julien benoit — January 22, 2013 @ 2:32 pm

Reply
It would definitely be of interest. Very cool.

Comment by nmiller — January 22, 2013 @ 4:33 pm

Reply
Yes, definitely. For some families this would be really useful.

Comment by Bruce Gow — January 22, 2013 @ 5:29 pm

Reply
It would be really interesting for helping maintain a proper standard.

Comment by RJ — January 23, 2013 @ 12:35 am

Reply
thought this would be possible…could come in handy

Comment by Arno — January 23, 2013 @ 2:17 am

Reply
Hi harry,

were can we get this add-in ? Is this a document macro or the user have to install it to be promped by a security password ?

Thanks,

Comment by Carl — January 23, 2013 @ 8:03 am

Reply
Sorry to be the only negative comment here but I could really see a password slowing down the entire work process.

Instead of restricting access, I would much rather just track who changed a family (and/or what they changed). One of the big issues here is that families exist in two places: the project & our standard family library (on the network). The customized families that exist in the project are not always the problem (until someone copies them into a new project).

In general, I guess I am just suggesting an idea for another Add-in that would not allow users to copy families or drafting views from project to project (forcing them to use the company standard families and drafting views). This seems to be where the real trouble lies.

Comment by Nick — January 23, 2013 @ 12:45 pm

Reply
- That’s an interesting thought. I’m curious to know if revit logs the location of the source file of a copy to clipboard. If so, I would think there would be a way to prohibit a copy paste if the source of the copy isn’t from a particular location (i.e. the network library). I’m assuming this info is retained in memory somehow. Assuming what I’ve mentioned is possible, you then could allow certain locations (i.e. the network library or a project specific admin folder) to be the only locations in which families can be loaded).
  
  Comment by David — January 24, 2013 @ 7:40 am
  
  Reply
This is a great idea…I have office standard system families in the template and it would be nice if they became untouchable…Don’t know if it is possible to password protect system families individually…

Comment by Mark — January 23, 2013 @ 1:36 pm

Reply
Hi Harry,

Great idea – looking forward to testing this one out.

Ben

Comment by Benjamin Malone — January 24, 2013 @ 4:47 am

Reply
The concept of this idea sounds wonderful. I am looking for a way to protect my library from being used by other firms. This would be one of the best add-ins I have ever seen if so.

Comment by Tracy Givin — March 20, 2013 @ 3:50 pm

Reply