These best practices help you get the most value from Nexus while staying in control of your tools and data. You don’t need to be technical — small habits make a big difference.

‍

#1 Connect only the tools you actually use

Start by connecting the tools you rely on most.

  • This keeps results focused and relevant
  • It’s easier to understand where answers are coming from
  • You can always add more tools later

If a tool isn’t helping, you can remove it anytime.

‍

#2 Review your connected tools regularly

It’s a good idea to occasionally check which tools Nexus has access to.

  • Remove tools you no longer use
  • Reconnect tools if access has changed
  • Keep permissions up to date

A quick review helps keep things tidy and secure.

‍

#3 Be clear when you ask for help

Nexus works best when your request is specific. Clear requests lead to clearer results. Instead of:

  • “What’s going on?”

Try:

‍

#4 Start simple, then go deeper

If you’re new to Nexus, begin with basic tasks. Good starting points:

  • Finding information
  • Summarizing documents or conversations
  • Getting highlights or updates

Once you’re comfortable, try asking for insights, comparisons, or patterns.

‍

#5 Use Nexus for insights, not just answers

Nexus can help you understand what’s happening, not just show you data. Try asking:

#6 Keep permissions in mind

Nexus can only work within the permissions you approve.

  • If Nexus can’t access something, it may need permission
  • If you remove access, related requests will stop working
  • You’re always in control of what Nexus can do

‍

#7 Clean up when you’re done

If you connected a tool for a one-time task or test, disconnect it when you’re finished. You can reconnect it anytime. This helps:

  • Reduce clutter
  • Limit unnecessary access
  • Keep your setup simple
    ‍

#8 When in doubt, ask Nexus

You don’t need special commands or perfect wording. Nexus is designed to work in plain language:

  • Ask Nexus what it can help with
  • Ask it to explain or rephrase results
  • Try a follow-up question