Portfolio

Application development

Streamlining file upload and storage

1: Insecure manual upload

 

A leading global provider of services in debt collection, confidential credit control, and tracing was looking for improvements to their system for UK client file uploads.

 

With no dedicated applications in place, clients were required to send spreadsheets, documents, or images regarding outstanding debt as emails or third-party file transfer platforms.

 

This created a problem of low security for sensitive information and made collaboration or transfer of files between departments and teams difficult and disorganised. All of this had the effect of hampering productivity and performance.

2: Custom PHP development

 

The Influential Software team designed and built a bespoke web-based application, accessible to any internal team, that allowed clients to upload files directly to the company’s storage. Our developers ensured security through rigorous penetration testing and a role-based system that only permitted client users to view their own files.

3: Collaboration and compliance

 

Our web-based application provided easy and flexible accessibility for both clients and internal teams, with security risks brought down to a minimum.

 

The company was satisfied with both the solution and our team’s seamless build and deployment. Based on the success of this project, extra administrative features are being discussed for future development.

 

Are manual processes affecting your productivity?

Our development team will provide a solution.

Info

15th May 2020
development, application, PHP, financial services

Privacy Preference Center

Necessary

Advertising

Analytics

Analytics cookies collect information that is used either in aggregate form to help us understand how our Websites are being used or how effective our marketing campaigns are, or to help us customise our Websites for you.

Google Analytics
The cookie _gcl_au is used by Google Analytics to understand user interaction with the website.

For example, in order for Google Analytics to determine that two distinct hits belong to the same user, a unique identifier, associated with that particular user, must be sent with each hit.

The analytics.js library accomplishes this via the Client ID field, a unique, randomly generated string that gets stored in the browsers cookies, so subsequent visits to the same site can be associated with the same user.

By default, analytics.js uses a single, first-party cookie named _ga to store the Client ID, but the cookie's name, domain, and expiration time can all be customized. Other cookies created by analytics.js include _gid, AMP_TOKEN and _gac_. These cookies store other randomly generated ids and campaign information about the user.

Google Analytics
_gcl_au, _gid, _ga, gtm_preview

Other

WordPress uses cookies for authentication. That means that in order to log in to our WordPress site, you must have cookies enabled in your browser.

There are two types of cookies set by WordPress.
1 — Session cookies — These are ‘strictly necessary’ cookies as WordPress will not be able to function without it.
2 — Comment cookies — These are not ‘strictly necessary’ cookies and are set when users leave a comment on a post.

Wordpress Session cookies:
Users are those people who have registered an account with the WordPress site.
wordpress_[hash]
wordpress_logged_in_[hash]
wordpress_test_cookie
wp-settings-{time}-[UID]

Wordpress comments:
Comments are usually turned off by default.
If by chance they are still active on a post, asides being turned off when spotted, data from these are not saved by Influential.
- When visitors comment on a post, they too get cookies stored on their computer. This is purely a convenience so that the visitor won’t need to re-type all their information again when they want to leave another comment. Three cookies are set for commenters:
comment_author_{HASH}
comment_author_email_{HASH}
comment_author_url_{HASH}

Wordpress, Intercom
comment_author_{HASH} comment_author_email_{HASH} comment_author_url_{HASH} wordpress_[hash] wordpress_logged_in_[hash] wordpress_test_cookie wp-settings-{time}-[UID]
intercom-id-[app_id],intercom-session-[add-id]