JobAdder: Dashboard The Dashboard shows an overview of signing metrics in the current billing cycle for the Secured Signing account, including: Total Documents; total documents used in current billing cycle and percentage change compared with the previous cycle. Total Signed; total documents signed in current billing cycle and percentage change compared with the previous cycle. Total SMS; total SMS used in current billing cycle and percentage change compared with previous one. Completion Rate; proportion of initiated signing process’ that have been completed. Document Status; overview of signing process status (Sent, Complete, and Incomplete). Document Volume; Number of documents used for each of the last 12 months. Completion Time in Hours; Average document completion time for each of the past 12 months.
JobAdder: My Account From one of following records, Open Secured Signing in the Action menu, and select Admin: Candidate Job Application Placement Company Contact My Account shows the Account information of the user in Secured Signing platform You can review your Secured Signing account summary Name: the name of your Secured Signing account; showing in the Secured Signing email Email: the email of your Secured Signing account; used in Secured Signing emails Account Status: the status of your Secured Signing account Account Plan: the plan of your Secured Signing account Documents Used: documents used in current billing cycle
JobAdder: Reports You can run reports to have an overview across selected data ranges from your Secured Signing account. Invitee Report: shows documents grouped by invitees. Document Report: shows the basic document signing process. Activity Report: shows account activities. Pending Report shows documents waiting to be signed or completed. Expired Documents Report: shows documents expired signing process. Witness Report: shows documents grouped by witnesses of the invitee. SMS Report shows SMS usage and sending status. Detailed Document Report: shows the full document signing process. Email Bounce Report: shows the details of bounced email, if the email failed to deliver and Secured Signing has been notified
JobAdder: Document Status View Document Status shows all In Progress documents related to Candidate, Job, Application, Placement, Company, and Contact. If the user role is Collaborator, you will see the details of all in-progress relating to the record type you have selected or a viewing in. If the user role is Standard, if you didn’t send the document, you will not see other in-progress documents sent by other users. We recommend to make users Collaborators so you can see each other’s pending documents for better visibility on the record. In Progress: Documents that have been sent out but not completed Signed: Document that have been completed within the last 7 days. After 7 days, the signed documents will not appear here but they will have been saved back to JobAdder files section. They save back to JobAdder on completion of document or document pack. You can also manage the signing process using the buttons below. You can see / action: – The document sent out. – Real time audit log. – The email invitation sent. – Verify signatures. – ‘i’ to change the signing process such as, due date, email address, First & Last Name and send a manual reminder. – Delete the signing process is you’ve told they no longer want to sign.
JobAdder: Create Automated Workflow Process with Secured Signing Triger the automatic sending of document or packs of documents when changing a status of a record in JobAdder. For example, when moving a candidate to Placed Status, you can send out the employment contract automatically.
JobAdder: How to Create & Send Document Template with Secured Signing You can create document templates within Secured Signing, using JobAdder data. For example, create template for employment contracts, terms of business and much more. Watch the video below to learn more.
ADFS 2.0: Configuring Single Sign On for Secured Signing using Active Directory Federation Services Setting up active directory federation services for use with Secured Signing will allow the nominated users within your domain to use the Secured Signing service using their network credentials. When the single sign on option is enabled in Secured Signing, logged in users will not need to enter their username and password in Secured Signing. The configuration process requires:Activation and configuration of federations services within Active DirectoryAdd Secured Signing as a relying party trust in ADFSConfiguration of your Secured Signing membership to accept authentication against Active Directory using federation services. Install and Configure ADFS 2.0 If not already installed, download & install ADFS 2.0. The software is available through here.NOTE: Don’t install the ADFS role from server managementIf you are using Windows Server 2008 R2, you will need to apply the ADFS 2.0 hot fix. Download it from this link.Prepare a valid ssl certificate (.pfx file, with private key). This certificate will be used by the ADFS federation service website, so it should be valid with your ADFS website domain name.2Import this certificate to IISOpen IIS, click server node, double click Server Certificates, then click Import at the right action panel Configure the ADFS 2.0 Federation serviceRun ADFS 2.0 Management Console as domain administrator. Run Create new federation service wizard. Use the certificate imported above to finish the configuration.In IIS manager, go to the Default Web Site/adfs/ls application,. Double click Authentication, enable Windows Authentication. In the advanced settings window, select Extended Protection to Off On IIS manager, add https bindings with above certificate to Default Web Site.Don’t change other default settings in IISIn ADFS 2.0 Management Console, find metadata xml path from right panel of “ADFS 2.0/Service/Endpoints”. It should be in the format https://your.domain.com/FederationMetadata/2007-06/FederationMetadata.xmlVerify the ADFS service is running by accessing the server: https://your.domain.com /adfs/ls/IdpInitiatedSignon.aspxEnable CROS for ADFS websiteAdd below lines to the web.config under Default Web Site/adfs/ls application directory <system.webServer> <httpProtocol> <customHeaders> <add name=”Access-Control-Allow-Origin” value=”*” /> </customHeaders> </httpProtocol> </system.webServer> Optional: set token caching time in the power shell console: > Set-ADFSProperties -SSOLifetime 5 > Set-ADFSRelyingPartyTrust -TargetName adfs.dsx.co.nz -TokenLifeTime 5 > Set-ADFSProperties -ReplayCacheExpirationInterval 5 > Set-ADFSProperties -SamlMessageDeliveryWindow 5 Restart the ADFS 2.0 service and IIS Add relying party trust Once ADFS 2.0 is ready, add a new relying party trust to the ADFS 2.0 service.In the ADFS 2.0 console, run “Add Relying Party Trust” wizard.Click “Start”, select “Enter data about the relying party manually” option and click “Next”.Enter a display name and click “Next”Select “ADFS 2.0 profile” options and click “Next”You can Ignore the encryption certificate, so just click “Next”Enable both WS-Federation Passive protocol and SAML 2.0 WebSSO protocol. For both protocols input https://www.securedsigning.com/ADFS/Account/LoginCallbackAdfs as endpoints and click “Next” Input https://www.securedsigning.com/ADFS/Account/LoginCallbackAdfs as identifiers and click “Next”Please notice that the rely party identifier is case sensitive. Please input the exact value. Select the > Permit all users to access this relying party option and click Next Click Next and CloseIn the popup claim rule window, add a new Transform Claim Rule In the popup wizard, select Send LDAP Attributes as Claims and click Next Input the rule name, select Active Directory as the Attribute store and select the LDAP attributes below E-Mail-Address -> E-Mail Address Surname -> Surname Given-Name -> Given Name User-Principal-Name -> Windows account Name Click Finish Setup Single Sign On with ADFS in your Secured Signing Membership You need an enterprise account to integrate secured signing with your own ADFS server.Login to the Enterprise Portal and go to Memberships.Select the membership that requires single sign on with ADFS. In the Single Sign On tab. Enable Single Sign On and input your Federation Metadata Address. Click Users Setup button. This will open the Accounts management page where you can manage your accounts to use ADFS integration. All accounts under this membership must login with ADFS. Users will no longer be able to authenticate using a username and password to access Secured Signing. Select an account from the account list, input the User Domain Name Login (ADFS) and save. This Single Sign On input option is visible only when the Single Sign On has been enabled for the membership. The User Domain Name Login should be in the format ‘Domain\Windows Account’. This should be the User logon name (pre-Windows 2000) property from Active Directory User properties. The “User Domain Name Login” is case insensitive. It should not be duplicated (use same domain name for different accounts) in one membership. You need to setup all accounts for ADFS login. Activate user account Once user account created, the user will receive an activation email, click Click to Activate button in the email. Then in the activation page, click Activate button. Join an Existing Secured Signing Account to a Membership with Single Sign On enabled For an existing user, they can join a membership by adding the membership code to the My Account > My Details page If this membership is configured to use Single Sign On with ADFS, the user will need to enter tjheir User Domain Name Login and click “OK” to join the membership.Initial Login with Single Sign On (ADFS)Once single sign on is enabled, the first time each user accesses Secured Signing they will need to input their email to login. A password is not required.The system will check if Single Sign On is enabled for this user. If so, it will redirect to your ADFS server website. Then the user input his/her windows logon credential to login with your ADFS server. The user can check the option to “Remember my email” to login with ADFS next time.Once the user has logged in with ADFS successfully, the user will be redirected to Secured Signing. On subsequent logins, the user’s domain name will be remembered. Click “Log in with ADFS” the user will be logged in to Secured Signing using the domain name to login.Please notice that, with this option, you should logon to windows with your own account to login with ADFS. Otherwise, you may see an error saying “Cannot login, use your own computer to retry or contact your administrator.”.