Talked about this one with Don a few months ago. The idea was to create a "Person" entity records that would not log in. I had a certain function in mind, but since then I've found an even more mundane reason: contact lists.
We are importing client lists into SG, and decided against creating a custom entity for tracking them. After all there already is a "Person" entity in the database; why re-invent the wheel in a separate table?
We've been importing our client address books with (some) success, but I've found a number of things I'd love to see tweaked to make this work better. To wit:
- Add a "non-login" permission group. Right now I am getting around this by specifying a blank "permission group" field on bulk import. "No Permission Group" is essentially my ersatz "non-login" type for now. (Attached Picture 29.) Ideally I'd love to see user-definable permission groups, but that plays into the larger permissioning functionality discussion.
No email to non-login users - via Notes, etc.. I ensure this by disabling all email optins for these accounts; and by ensuring that none of them are added to projects. However, having an absolute fail-safe built into the back-end would be nice. That way we never accidentally copy a client on internal correspondence.
- Do not require login or password for "non-login" users. (In effect, we are treating "People" like our own Open Directory. And no, I'm not going to request LDAP integration right now!) Getting around the login/password requirement plays a little bit of havoc with the bulk importer, although there are workarounds.
- Finally, do not auto-suggest non-login users on "People" entity fields. When you have a few thousand records, there are suddenly twenty "Bens". I only need my artist Ben, not the post coordinator at Focus, or the PR guy from BMG. (Attached Picture 30.)
Curious whether other SG users are using/abusing the "People" entity in the same way.