> You are reading the Docusign Developer Documentation. For clean Markdown of any page, append .md to the page URL.
>
> Documentation indexes by section:
> - APIs and SDKs: https://docusign.docs.buildwithfern.com/docs/llms.txt
> - Platform 101: https://docusign.docs.buildwithfern.com/platform/llms.txt
> - Extension Apps: https://docusign.docs.buildwithfern.com/extension-apps/llms.txt
> - Docusign CLI: https://docusign.docs.buildwithfern.com/docusign-cli/llms.txt
>
> Authentication (OAuth, JWT Grant, M2M): https://docusign.docs.buildwithfern.com/platform/auth
> Webhooks and Connect: https://docusign.docs.buildwithfern.com/platform/webhooks
>
> OpenAPI specifications: https://docusign.docs.buildwithfern.com/openapi.json
> MCP server: https://docusign.docs.buildwithfern.com/_mcp/server

# Preventing Embedded Sending users from accessing an account

For the eSignature REST API methods EnvelopeViews:createSender (embedded sending) and EnvelopeViews:createCorrect (embedded envelope correct view): If the returnUrl attribute is set, then the user is no longer able to access other sections of the Docusign web app by changing the url in the browser. A Special case is if the returnURL attribute is set to [https://www.docusign.net](https://www.docusign.net) (or [https://demo.docusign.net](https://demo.docusign.net) for the developer system) then the user will be redirected to the Docusign web app after completing their use of the sender or correct view. They will need to login if they do not already have an active login session.

[Learn More](/changelog/12-01-2020-7)