CiviCRM Community Forums (archive)

An organization I work with has a work flow like this:

1. New people are added as CiviCRM contacts.
2. They are added in the "Pending" state to some group (typically, this is by Organic Group via civicrm_og_sync).
3. An admin who has an ACL on that group makes a decision about the new contact, and accepts or rejects them for the group.

The problem here is that while the contact is only "Pending" on that group, the admin does not yet have view permission on the contact.

I can work around this by playing games with Smarty and instead of putting a link to the contact's summary page (which the admin can't yet see), construct my own fake summary page that gives the admin enough information to make the decision.  But I'd prefer to use the summary page, since after all, that's what it's for.

Is there any way to work around this?

Thanks, Xavier.

Well, it's closer.

One problem here is that for a variety of organizational reasons, it's important that if admin A and admin B have separate domains (general sense of the word; not a CiviCRM "domain") of authority, that they will be unable to see each other's contacts.  In this "Pending" case, the user who's possibly moving from A's domain into B's domain has initiated the action, so it's reasonable that the the new admin can see the potential member.

The other potential is that you could end up with an awful lot of extra ACL groups with this method.

I'll need to talk to the client to see how sensitive they are to this issue.  It may be that I can get away with granting this access at a higher level in their hierarchy.

Who said ACLs weren't fun :-)

Rob