I need an experienced technical architect
Budget: £36 – £0 GBP
Starters and Leavers Process
Sales Requirements
An automated system that clients can use to request a new starter or notify that someone is going to leave.
This should not be a Word/PDF form, but web based [see Form Requirements]. It should be able to be tailored for specific client requirements (such as access to specific SharePoint libraries, specific applications, etc.), a standard permissions model applied and associated approval.
Once approved by client, it should as a minimum raise a ticket for the ServiceDesk to undertake any actions required. Ideally (potentially phase two) it should automatically create accounts and apply permissions.
Critically it needs to allow us to automatically know the number and list of current users at any point. This should be reflected (maintained?) in Autotask to ensure we are only providing support to contracted users (this is important from both financial and security perspective).
The leavers process needs to be fully defined (i.e., do we forward emails to another person, archive mailbox, etc.) and automated.
Form Requirements
Online Form – an online form that clients can easily fill in (ideally with mobile device support) accessible via link (sent in email) or website (ideally subdomain of syntax.co.uk)
Modern Look – the form should look modern and have flexible elements such as images, text, radio buttons, dropdown, date picker, etc.
Standard/Tailored Forms – a standard form and additional fields tailored to specific clients (when essential, we should look to standardise and be prescriptive as much as possible)
Conditional Logic – the form should have conditional logic, i.e. subsequent fields can change based upon user input
Client Sign-off and Audit Trail – it should be possible to have a record (ideally immutable) of the request details and who requested it with date/time. Potentially integration with DocuSign
Workflow – support multiple people approving/validating the form (potentially internal Syntax review?)
Export Format – completed information should be accessible/saved in table format. Can also be sent to ServiceDesk to action in a format (such as text file or CSV) that can easily entered without error into Datto PSA or further automated (ideally automatically create ticket)
Integrations – integrations with SharePoint, Power Automate, and DocuSign. Salesforce and API may be useful for further automation
Potential Phases
1. Online form that captures data and emails to ServiceDesk and stores the data in some form of table/database
2. Adds integration with Autotask to add/remove users to list of supported users
3. Adds automation to add/remove accounts, allocate licences, permissions, etc.
Sales Requirements
An automated system that clients can use to request a new starter or notify that someone is going to leave.
This should not be a Word/PDF form, but web based [see Form Requirements]. It should be able to be tailored for specific client requirements (such as access to specific SharePoint libraries, specific applications, etc.), a standard permissions model applied and associated approval.
Once approved by client, it should as a minimum raise a ticket for the ServiceDesk to undertake any actions required. Ideally (potentially phase two) it should automatically create accounts and apply permissions.
Critically it needs to allow us to automatically know the number and list of current users at any point. This should be reflected (maintained?) in Autotask to ensure we are only providing support to contracted users (this is important from both financial and security perspective).
The leavers process needs to be fully defined (i.e., do we forward emails to another person, archive mailbox, etc.) and automated.
Form Requirements
Online Form – an online form that clients can easily fill in (ideally with mobile device support) accessible via link (sent in email) or website (ideally subdomain of syntax.co.uk)
Modern Look – the form should look modern and have flexible elements such as images, text, radio buttons, dropdown, date picker, etc.
Standard/Tailored Forms – a standard form and additional fields tailored to specific clients (when essential, we should look to standardise and be prescriptive as much as possible)
Conditional Logic – the form should have conditional logic, i.e. subsequent fields can change based upon user input
Client Sign-off and Audit Trail – it should be possible to have a record (ideally immutable) of the request details and who requested it with date/time. Potentially integration with DocuSign
Workflow – support multiple people approving/validating the form (potentially internal Syntax review?)
Export Format – completed information should be accessible/saved in table format. Can also be sent to ServiceDesk to action in a format (such as text file or CSV) that can easily entered without error into Datto PSA or further automated (ideally automatically create ticket)
Integrations – integrations with SharePoint, Power Automate, and DocuSign. Salesforce and API may be useful for further automation
Potential Phases
1. Online form that captures data and emails to ServiceDesk and stores the data in some form of table/database
2. Adds integration with Autotask to add/remove users to list of supported users
3. Adds automation to add/remove accounts, allocate licences, permissions, etc.