Getting set up with email

Using user email addresses

One of the requirements in Jive communities is that users must have unique email addresses. This allows user's email addresses to be used as user names within communities.

Despite that, we recommend that you do not set Jive user names to be the email addresses of users. If you do this, the user's email address string show up in the user's profile page URL, even if email visibility is set to Private To User.

If you are using SSO for authentication, you should set it to authenticate each user's user name.

For more information, see Configuring incoming email.

Configuring outgoing SMTP email server

Jive uses an outgoing SMTP email server for sending messages, such as content update notifications, task reminders, and registration confirmations. You can do this manually in the Admin Console or during the setup process via the Setup wizard.

For more information, see Configuring outgoing (SMTP) email and Configuring application with the Setup wizard.

Configuring incoming email server for creating content via email

You can enable features through which people can post content to the application by sending email to a particular address. For that, you should set the connection to an incoming email server so the instance can receive email messages from users. You can do this manually in the Admin Console or during the setup process via the Setup wizard.

For more information, see Configuring incoming email and Configuring application with the Setup wizard.

Disabling email in test environments

In test environments, you can temporarily disable email to and from the application. Your production instance is typically set up to both send email notifications (SMTP) and access an email account (Email Monitor) or server (Advanced Incoming Email). In your test production instance, you can temporarily change these settings; otherwise, you may find that the new test instance generates email notifications that look like they're coming from your production instance. This can be very confusing to users and might end up unnecessarily burdening your email servers.

For more information, see Disabling email in test environments.

Editing and localizing email templates

Jive includes a set of email templates for emails it sends to users in response to certain events. You may want to edit the default email notification templates to perform content changes or to include password reset notifications.

For more information, see Editing email notification templates and Localizing email notification templates.

Preventing email spam

There are a few email-related ways to help prevent spam in your community. For more information, see Spam prevention and Advanced spam prevention.