Support
Getting help, giving feedback, billing, and privacy.
Getting help
Contact your Customer Success Manager for anything to do with the nCino MCP: onboarding, registering a sandbox, questions about access, billing, turning the change tools on, or a problem you cannot resolve yourself.
If something is not working
| What you see | Usually means |
|---|---|
| Sign-in fails, or loops back to the sign-in page | Identity federation is not live yet, or the person signing in has not been enabled for it. |
| You sign in successfully but see no nCino tools | The connector is not enabled in that conversation or workspace. Check your assistant's connector settings. In Copilot Studio, also confirm generative orchestration is turned on. In Perplexity, turn the connector on for the chat. |
| An org is missing from the list, or shows a connection error | The org is not registered yet, or its authorization needs re-validating. |
| Results are incomplete, or the assistant says it cannot see something | The nCino Communicator user may be missing a permission in that org. |
| Something that worked before stops working | A sandbox refresh may have deactivated the nCino Communicator user, or your identity provider's client secret or signing certificate may have expired. |
| A change fails, or the assistant says a capability is not enabled | The change tools may be turned off for your institution, or the nCino Communicator user may not have permission to make that change. |
| You are asked to sign in again partway through a session | Expected in some assistants today. See Limitations. |
| Results look cut off | Narrow the request to one object, field, or release and ask again. |
If none of those explain it, contact your Customer Success Manager. Including your AI assistant, its version, the org, what you asked, and the error you saw will get you to an answer faster.
Giving feedback
Ask your assistant to send feedback. Say something like "send feedback that there is no tool for X." It goes to the team that maintains the connector and changes nothing in your environment. Your assistant may also send feedback on its own when a tool falls short, and feedback can include examples of what was asked and what came back.
Feedback during early access shapes what gets built next, so it is worth sending.
Intelligence Units
Use of the nCino MCP consumes Intelligence Units from your institution's allocation. Each successful request your assistant makes on your behalf draws from it. Failed requests do not, and neither do connecting, signing in, or listing what the connector can do. Your assistant's own reasoning runs on your own subscription rather than being billed by nCino.
For the terms that apply to your institution, contact your Customer Success Manager.
Privacy
The nCino MCP is covered by nCino's public privacy commitments. It works with the nCino and Salesforce configuration and documentation you direct it to, in order to answer your requests.
- What reaches nCino. Only what your assistant puts in a request, such as an object name, a query, or the values for a change. Your prompts, chat history, and files stay with your AI provider.
- What passes through. What the tools read from your sandbox, and the result of each request, pass through nCino on the way back to your assistant. nCino does not keep a copy.
- What nCino keeps. Sign-in records, a log of each request (such as the capability, institution, org, time, and any error message), usage counts for Intelligence Units, your list of registered sandboxes, and any feedback your assistant sends.
- Documentation search. Documentation lookups send search terms to the search services behind nCino Community and docs.ncino.com.
Your AI assistant is a different matter. It retains the conversation, including any org data in it, according to its own policy. That is governed by your agreement with your AI vendor rather than by nCino, and it is the right place to look when working out where your data ends up.
For what nCino collects, how it is used and retained, and how to request deletion, see the nCino Privacy Statement.
Updated 9 days ago
