This checklist covers the 10 things to check before you launch your Brightidea site or your first Initiative. Use it to catch the setup problems that most often block emails, access, and evaluations.
1. Allow your system email address
Before you launch your first Initiative, test your system email address so that notifications are not blocked or marked as spam. Ask your email administrator to allow (whitelist) the Brightidea mail server.
Learn more: SPF & DKIM Requirements for Brightidea Email Communication
2. Set up single sign-on (SSO)
Administrators can connect Brightidea to your company's identity management system, so people sign in with their company credentials. If you plan to use SSO, set it up and test it before you invite users.
Learn more: Single-Sign-On (SSO) Setup Guide
3. Add your users and groups
You can load users into your Brightidea site before launch with the user import and the group import.
- Brightidea cannot import user passwords. After the import, each user goes to the login page and selects Forgot password? to create a password.
- The ALL group contains every user in your system. If you use SSO, anyone who has visited your system is in this group.
- If your site uses SSO, contact your Brightidea representative before you run an import, to avoid duplicate accounts.
Learn more: Command Center: People, Importing Users to Brightidea, and 'Group Import' in Brightidea
4. Check group access for each Initiative
Before you launch an Initiative, confirm that the correct user groups are assigned to it.
- A user must be in a group assigned to the Initiative to have access to it.
- An evaluator who is not in a group assigned to the Initiative cannot open any action items (evaluations) for it.
Learn more: Understanding Groups in Brightidea
5. Confirm the time zone and schedule
Confirm that your system is set to the correct time zone. The time zone controls when your Initiative starts and ends, when users have access, and when scheduled emails such as newsletters are sent.
- Users can submit ideas, vote, and comment only after the Initiative has started.
- When you use the Scheduler, confirm the start and end dates of the submission, voting, and commenting periods.
Learn more: Initiative Scheduler and Setting the Time Zone in Brightidea
6. Check your rules
The Rules Engine automates your pipeline. Each rule waits for an event, checks a condition, and then performs an action. Read through every rule before launch and confirm it does what you expect. A rule that is set up incorrectly can:
- Send emails in bulk.
- Send emails to the wrong recipient (submitter, admin, or group).
- Send action items at the wrong time or to the wrong evaluators.
- Move ideas to the wrong step.
- Conflict with another rule.
Learn more: Brightidea's 'Rules Engine'
7. Review your pipeline steps
- Confirm that each step has the correct evaluators assigned to it. Each step has a limit of 60 evaluators.
- A newly submitted idea lands in the first step of the pipeline.
Learn more: Getting Started with Brightidea Pipeline Management
8. Review your scorecard templates
Before you move ideas into a Scorecard step, review the scorecard template:
- The questions and each question type.
- The answers and the point value of each answer.
Learn more: Scorecard
9. Check domain restrictions
Domain restrictions limit access to users whose email address is in a domain you list. You can apply them at the system level and at the Initiative level.
Learn more: Applying 'Domain Restrictions' in Brightidea
10. Finish widget and design changes
When you finish adding or removing widgets on a page, select Disable Widget Setup Mode to avoid accidental changes.
If you bought custom design services or use a design template, some widgets on the system and Initiative home pages contain custom CSS, HTML, and JavaScript. Editing or deleting these widgets can break your site's design and features. Talk to your Brightidea representative before you make design changes.
Learn more: Configuring Widgets within Brightidea and System / Initiative Design Overview (Applying HTML and CSS)
Comments