How do I grant someone access to my SNDS account?

Email marketer from Reddit shares that setting up SNDS initially requires linking it to your sending infrastructure. Then each user who requires access has to request it.

Email marketer from Quora advises that the most secure method is for each individual to have their own SNDS account, tied to their own Microsoft account, requesting access as needed. Sharing login credentials introduces unnecessary security risks.

Marketer from Email Geeks shares that if Sendgrid owns the IP, they will have to approve the access request. If it's dedicated, inform your account manager to expect the request.

Marketer from Email Geeks explains that users need to create their own SNDS account and request access. Once they have access to the same IP range, they will appear in your account.

Email marketer from Email Deliverability Forum suggests that if directly granting access is problematic, consider creating reports and sharing them periodically. This avoids giving full access but still provides necessary insights. You can export data and share via secure methods.

Email marketer from StackOverflow explains if access isn't being granted, confirm the requesting user is using a Microsoft account associated with a valid abuse/postmaster address for the sending domain. Sometimes, domain ownership verification issues prevent access.

Email marketer from Email On Acid suggests that each member should use a unique log in rather than share credentials. This gives better visibility and tracking for users.

Email Marketer from Email Geeks mentions that if the colleague requests access and contacts Sendgrid support, they will check and approve the access. Contact support as soon as the request is made. There is a short window to approve SNDS requests, or the colleague may need to re-request access.

Email marketer from Reddit shares that the person needing access must first register for their own SNDS account using a Microsoft account. After registration, they submit a request for access, specifying the IP addresses. The original account holder will then receive a notification to approve or deny the request.

Marketer from Email Geeks confirms that it is normal to request access through an internal email address, but it's unlikely you'll receive the email unless you have a mailbox set up for it.

Marketer from Email Geeks mentions that if the colleague requests access and contacts Sendgrid support, they will check and approve the access. Contact support as soon as the request is made. There is a short window to approve SNDS requests, or the colleague may need to re-request access.

Marketer from Email Geeks explains that the user needs to click on 'request access' and enter the IPs they want to see. The IP owner (Sendgrid) will receive an alert about the request.

Marketer from Email Geeks shares that users request access via their SNDS account, and you grant it. You'll receive an email to abuse@ or postmaster@.

Expert from Word to the Wise explains that granting access requires the user to request access on their own. Sharing accounts causes confusion on who is using the account and can lead to issues for future use.

Expert from Spam Resource highlights the importance of individual accounts for security and audit trails. Sharing accounts introduces risks and makes tracking accountability difficult. Therefore, the best approach is for each person to set up their own SNDS account and request permissions.

Documentation from Microsoft explains that after a user requests access, the SNDS account administrator receives an email notification. The administrator must then log into their SNDS account and approve the request. The approval is tied to the IP address being requested, so ensure the IP is correct.

Documentation from Microsoft explains that SNDS accounts are individual. Users need to create their own account and request access to the specific IP ranges they want to monitor. The account owner then needs to grant access within the SNDS interface.

Documentation from Microsoft states the primary requirement is that the requesting user must have a valid Microsoft account. The user's email address used for the Microsoft account should ideally match the abuse or postmaster address associated with the sending domain, to make verification easier.