Yesterday’s post was about putting password protection on the Edit Type button in the Properties dialog. It was great to see so many comments and page views from people interested in this.
Here is another part of limiting access to modifying families – preventing unauthorized users from opening family files in the Family Editor.
This could be combined with the Edit Type password requirement shown yesterday but here are a few issues that would need to be resolved. It would be great to hear your ideas on these.
- Should these restrictions be applied to all families? If not, how should specific families be marked? Would a Yes/No type parameter in each family make sense? (It would be nice to able to add a family parameter instead of a type parameter, but the Revit does not support that.) Another option would be to mark families by storing some extensible storage data, but that introduces its own complexities.
- Should there be password restrictions on both opening existing families and creating new families?
- If I made this available as a single compiled application, everyone who downloads it would have the same application with the same password. Is this a deal-breaker?
Ideally every company would be able to set their own password, but having me generate a unique DLL for each firm seems a bit cumbersome for everyone.