Skip to main content
You probably have questions. Here are answers to the questions we hear most from admins like you.
Can’t find your answer? This is living documentation. If you have a question that should be here, reach out to support or ask in the community.

​
Organization & Setup

Yes! Go to Settings > Basic Configuration > General Settings and update it. Changes take effect immediately across all communities.
As many as you want, limited only by your plan. Check your plan to see seat limits. Need more? Upgrade anytime.
Not directly, but you can export content from one organization and import it into another using CSV exports. It’s manual but works.
It gets archived (you can restore it). Data is preserved for 30 days before permanent deletion. Always backup important data first.

​
Teams & Permissions

Yes! Set up team members with specific roles limited to certain communities. Admins can be community-specific or organization-wide.
Managers create and manage communities, challenges, and rewards. Editors create content but don’t manage communities or delete things. Think of editors as content creators, managers as community owners.
Go to Settings > Team Members, find the person, click their menu, select “Deactivate” or “Remove”. Their contributions stay; they just lose access.
Yes! Invite them normally, then remove them when the project ends. Consider using the Analyst role if they only need to view data.

​
Branding & Customization

No—in fact, it helps! Search engines prefer your domain over a generic one. Plus, it looks more professional to users.
Yes! Subdomains work great. Some admins use subdomains for different communities (team1.mycompany.com, team2.mycompany.com).
We provide color standards and font recommendations in settings. Stick to accessible colors (good contrast) and readable fonts.
Not directly through the UI, but if you need deep customization, contact support about white-label options.

​
Multi-Language

Nope! Start with essentials (org name, community intro), then expand. Untranslated content falls back to your primary language.
Depends on your budget. For 2-3 languages, professional translation pays for itself in user satisfaction. For testing, automated translation is fine initially.
No! You can archive languages anytime. Existing translations stay (for historical reference), but users can’t select it.
Use the language most of your users speak. If you’re global, English is a safe default, but pick what makes sense for you.

​
Content & Variables

10-20 tags is usually ideal. Too few and categories are too broad, too many and users get overwhelmed. Start with 10, expand if needed.
Yes! Variables work anywhere you write text. Use {user_name}, {team_name}, etc., and they’ll be personalized for each user.
Go to Tag Manager, find the tag, click “Bulk Apply”, and select which challenges/rewards to tag. Much faster than tagging individually.
Our system tracks answers and you can see trends, but custom scoring requires integration with your systems.

​
Integrations

Yes. We use industry-standard encryption and secure APIs. Never hardcode credentials, always use API keys with minimal permissions.
Your Nudj data stays. Data you sent to external tools depends on their retention policies. Check with them.
Yes! Send notifications when challenges are completed, users join, or rewards are distributed. Set up in Custom Integrations.
We retry failed webhooks up to 5 times over 24 hours. Check integration logs if they’re not arriving.

​
Troubleshooting

Check diagnostics (Settings > Advanced > Diagnostics). Filter by dates/reduce results. Clearing browser cache often helps.
Check: Is the challenge live (not draft)? Does the user have permission? Are there targeting rules excluding them? Review logs.
Check SMTP settings and email logs in diagnostics. Is sender address verified? Try a test send. Contact support if still stuck.
Deleted items go to archives for 30 days. Go to Settings > Advanced > Archive Management. After 30 days, it’s permanent.

​
Plans & Billing

Plans vary. Check our pricing page or contact sales. Most start with basic features and scale up as you grow.
Yes! Changes take effect immediately. Upgrading charges prorated, downgrading applies credit to future invoices.
Many organizations do! Reach out to sales and mention your nonprofit status. They can discuss options.
Usually all features for 14-30 days. Check during signup. No credit card required (usually).

​
Best Practices

Weekly minimum. Export settings, challenges, and rewards regularly. Critical data (user list) should be exported monthly.
Absolutely! Create a “staging” community where you test challenges, integrations, and settings before launching them.
Every community is different, but 1-2 new challenges per week keeps things fresh without overwhelming users. Adjust based on engagement.
Check analytics! Completion rates, average time, user feedback comments. What gets high completion? Do more of that.

​
Getting Help

Email support@nudj.com or click the help icon in the app. Response time is usually a few hours.
Yes! Check the community section. Other admins often have solved your exact problem.
Most plans include setup help. Some include 1-on-1 onboarding. Ask during signup.
Absolutely! Sales team loves demos. Book one.

​
Still Have Questions?

Reach out: We’re here to help.