iPad Notary Header

Hi Ryan, Were you embedding the notary signing ceremony or you logged onto the account? If you were embedding, could we try adding a "?iframe=true" at the end of your generated link, it should force the page to render in iframe mode, which is to hide the logo, breadcrumbs, session bar and global navigation. Also, can we make sure that the breadcrumbs, session bar and global navigation are disabled from package settings? They are all under the "settings"--"ceremony"--"layout"--"header"

{
  "settings": {
    "ceremony": {
      "layout": {
        "header": {
          "breadcrumbs": false,
          "globalNavigation": false,
          "sessionBar": false
        }
      }
    }
  }
}

Duo

Duo, I am setting the sessionBar to false but it is still being displayed on the signing. Is there something else I need to change in order to make it disappear?

Hi Ryan, I got an iPad with me and now I can reproduce the issue. I believe it's a more general issue that in-person including notary signing in tablet wasn't shown in iframe mode. I checked with our support team that there's a feature allowing you to choose Mobile Signing Ceremony instead of desktop mode in tablet, you can toggle the feature on by sending support team a request. This would be a quick solution to your requirement, at the same time, we can have a support ticket reporting the issue. BTW, did notary signing worked fine on your mobile? During my test, I can't see the change signer button, which should be displayed on right top. Duo

Duo, Yes, can we please get a support ticket going for this? From my understanding we do not allow our notaries to use the mobile signing experience for the exact same reason as you sated. They are not able to switch borrowers while on a mobile. Thanks for verifying this for us.

Hi Ryan, I just got some reply from our R&D team that this issue is caused by double redirection: load balance first redirect the page to a link with "?iframe=true", while because you were using tablet, Mobile Signing Ceremony redirected the page again and this second redirection removed the parameter from the URL. This fix has already been done and merged in development branch and will be available in next release. Duo