Invite Other Admins To Help (Manage Posts)

Unlike Web or Sermons, where you technically could manage each of those entirely on your own, Posts is unique in that, it almost necessitates multiple admins helping to run the show. That's because Posts is one of your church's strongest tools for communication with your congregation for all of the ongoings at your church. And it's very unlikely that you are the sole person running all of the diverse ministries, small groups, and events at your church plus creating the weekly bulletin.

So it's time to invite the head organizers/leaders in charge of church activities to manage their specific communications with their particular groups within the congregation (i.e. their audience).

In this guide, we'll cover the following topics. Click on any one to jump ahead.


A Reminder About Unique Login Credentials

Before continuing, it's important to note how login credentials function within Nucleus.

First, every login created for Nucleus also creates a personal My Nucleus account.

Second, anyone with a login can be invited to help manage your church's Nucleus account. They can use the same unique login to access both your church's account and their personal account.

Note: You can also invite someone who doesn’t yet have a Nucleus login. Once you send an invite email to them, they’ll just be prompted to create a login before being able to access your church’s Nucleus Dashboard.

Because each login has a personal My Nucleus account associated with it, we strongly recommend not creating logins that use a generic church email, or sending admin invitations to generic church email addresses.

Doing so presents opportunities for personal information of an admin to be associated with that account, which a future admin who takes over their position can then potentially see. (This could include giving history, payment methods, prayer requests, and more.)

Note: For a more in-depth review about Nucleus Accounts and unique login credentials, check out this guide, and then come back to this one.


Choose Who You Want To Invite

Inviting someone to help manage your Nucleus account is super easy! (And in case you need to revoke someone's access, that's easy too. But for now, let's focus on the more exciting task at hand: sending an invitation 😊)

To begin, there are two places you can invite admins:

  • In your Church Settings, where you can invite people to access any of the products you’re subscribed to.
  • Directly in Nucleus Posts, which will only allow you to invite people to help manage that specific product.

We already have a guide exploring how to invite people to help manage all your products from within your Church Settings here, so right now we’ll focus on inviting people specifically from within Nucleus Posts.

Note: You can invite as many or as few people to help manage any product in Nucleus, so once you’re finished inviting one person, you can restart the process to invite someone else too!

To do this, in Nucleus Posts, click on Manage and select AdminsClick here for a quick link.

[screenshot]

Next, click the + Add New button. Then in the fields that appear, enter in the person’s name and email address you want to invite to access Nucleus Posts.


Set Access & Permission Levels For The New Admin

Next, you can assign the level of admin permission you'd like to give this person:

  • Manager — Access to view and manage everything, including admins.
  • Assistant — Default access to view, manage, and publish most things except manage admins and some larger site-level controls (design, settings, and domains).
  • Volunteer — Default access to view, create, and edit post content and collections (no archive or delete).

After this, you can choose what kind of people record permission this admin has:

  • View Only
  • View & Edit
  • View, Edit & Create

[screenshot]

People record permissions may seem a bit out of context when providing an admin with access to Nucleus Post because there currently doesn’t exist any place within Nucleus Posts where you can access people records.

However, because people records can be accessed in multiple different products (like People + Messages, Giving, and Flows), these permissions are set platform-wide, rather than per product. So that’s why you’re able to set a new admin’s people record permission level here, since an admin can be invited to help manage multiple products.


Send An Invite Email To The Admin

After you’ve set up the initial access and permission levels, it’s time to click the Invite button.

[screenshot]

At this point, an email will have been sent from hello@nucleus.church to that person’s address. That email will look like this 👇

[screenshot]

Clicking the Accept Invite button will open a new tab in their browser with a place to login to access your church's Nucleus account.

If they've already created a personal My Nucleus account with that email address, they can login directly there.

If they've never created a login yet, they can click the create an account link and follow the prompts on the screen.

[screenshot]

Be sure to advise each new admin who accepts your invitation to check their email again for another message from Nucleus to verify their email address. This is super important, as verifying your email address is necessary for security purposes and also ensures each admin can enjoy the full range of their specific admin access levels and permissions.

[screenshot]

If you're unsure whether an admin has accepted the invite, you can always check the status in your list of Posts Admins here. If they’re yet to accept the email invite, their status will be Pending. If they’ve accepted it, it will say Active.

If the email has gotten lost in the admin's inbox, you can always click the Resend Invite button.

[screenshot]

Of course, you can also revoke someone’s admin access if they no longer require it. Simply click the down arrow beside the Edit Access button and select Revoke Access.

[screenshot]


Manage Current Admin Access

While viewing your admins in Nucleus Posts here, click Edit Access to amend someone's permissions to Nucleus Posts.

[screenshot]

Here, you’ll be able to select whether you want the admin to have General Access, Per-Collection Access, or Both (a hybrid approach) to Posts.

For General or Both, you can set the following permission level:

  • Manager — Access to view and manage everything, including admins.
  • Assistant — Default access to view, manage, and publish most things except manage admins and some larger site-level controls (design, settings, and domains).
  • Volunteer — Default access to view, create, and edit post content and collections (no archive or delete).

[screenshot]

When assigning someone access to a specific Collection, you will be able to type or click the dropdown menu to select a particular Collection. Then assign them with Assistant level access. You can do this with as many or as few Collections as you'd like.

[screenshot]

Once you click Save Changes, that person's permission level will officially be updated.


General Admin Management

This guide has specifically focused on inviting admins to access Nucleus Posts. If you’re interested in learning how to manage your admins across all Nucleus products, you can do so within your Church Settings.

[screenshot]

Note: You’ll need admin access to Church Settings in order to view this in your Dashboard.

We have an entire guide dedicated on how to Manage Admins In Nucleus. Many of the same instructions and principles discussed above will translate to managing admins in your Church Settings, so you’ll already be a step ahead if you haven’t yet managed your admins there 😎


What Next?

Now that you've explored the basic components of Posts to get everything up and running, now it's time to learn how to fine tune all the settings for your Posts, Collections, and Hub. Here are some excellent resources to propel you forward:

  • Adjust A Post's Advanced Options
  • Add & Manage Your Collections
  • Manage Collection Subscribers & Smart Campaigns
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.