Permission Request / Problem

Most permission request tickets resolve quickly once the admin has the right details — the key is submitting a clear, complete request the first time.

• Confirm the exact scope before submitting — specify which group email(s), shared drive(s), or platform (Chase Connect, Meta Business Suite, Facebook, etc.) need to change, and whether it's an add, remove, or both. Vague requests cause back-and-forth delays.
• Include the effective date and duration — if access is temporary (e.g., vacation coverage), state the start and end date in your request. This allows the admin to schedule the change and reversal without a follow-up ticket.
• Check whether access already exists (admin can verify) — several tickets resolved instantly because the user was already a member and just needed to confirm. Before submitting, ask your manager or a colleague if the access may already be in place.
• For group email delivery issues, wait a short time and retry — at least one case resolved on its own without any configuration change. If messages still aren't arriving after an hour, file a ticket noting the specific group address affected.
• For Meta Business Suite / Facebook page access, note that this is handled by the Marketing team, not IT. Route your request accordingly to avoid reassignment delays.
• For Chase Connect or Chase Mobile Deposit access (admin only) — the admin will send an email invitation from Chase; the requester must complete setup and download the authenticator app. Reach out to the admin directly if the invitation doesn't arrive.

If none of these solve it, file a ticket and include: the full name of the person needing access, the specific group email address or shared drive name, the platform (Gmail, Google Drive, Chase, Meta, etc.), the desired effective date, and whether the change is permanent or temporary.