Another way would be to customise your single sign on system such that user A's credentials can also be used to access user B's account (but only one at a time). Alex's suggestion is more seamless, but may not be enough, and there is no concept of ACLs for mailboxes (yet).
Sam On Sun, Apr 13, 2008 at 12:58 AM, Alex (Google) <[EMAIL PROTECTED]> wrote: > > Hi Calvin, > > One approach would be to set up a forwarding rule from A to B: > > http://mail.google.com/support/bin/answer.py?answer=10957 > > And to set up B to send as A: > > http://mail.google.com/support/bin/answer.py?answer=22370 > > With this approach A and B's email can get out of sync. > > You may find more ideas in the general Google Apps discussion group: > > http://groups.google.com/group/apps-discuss > > -alex > > On Apr 10, 3:55 pm, Calvin Dodge <[EMAIL PROTECTED]> wrote: > > I'm doing some advising for a local nonprofit in Tucson. They're > > looking for a robust and cheap email solution, and I've been > > suggesting they get a Google Apps account. > > > > Their problem with this is that they need email delegation - i.e., > > User A granting User B the right to send email as User A. I see hints > > that this is possible with Google Apps and 3rd party software, but > > have found nothing concrete yet. > > > > Can anyone point me to such 3rd party software? > > > > Thanks, > > > > Calvin Dodge > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Apps APIs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-apps-apis?hl=en -~----------~----~----~----~------~----~------~--~---
