Skip to main content
Royer Adames, home

Jump

Mitsubishi contract risk
Showing still 1 of 1

ProjectsMitsubishi contract risk

Mitsubishi contract risk

Through Integris, I worked on settings and frontend/backend permission controls as part of the Mitsubishi project team.

Private. Not available to the public.

Stack

  • Python
  • Flask

What it is

Team-built internal contract-management software for Mitsubishi, delivered through Integris. There is no public product demo.

Why it exists

Mitsubishi needed to organize and filter its contracts while limiting who could access the tool and change permissions. My part was the settings and permission-management work.

How it works

The team built the contract dashboard and filtering options. I built settings and permission controls across the interface and Python/Flask backend so authorized users could change permissions. The client accepted the handoff and began using the tool.

What I did

  • Responsive UI: Consistent layout across devices on the contract risk platform.
  • System security: App security and access management for sensitive data.

Story

Getting into a contract-management tool is only part of the job. What should someone be allowed to do once they are inside, and who gets to change that?

After leaving Echelon Fitness, I joined Integris. The agency brought together a small team, supported by a scrum manager, for a Mitsubishi contract-management project. The client needed an internal tool to organize its contracts, filter them by concerns such as security and priority, and work through them in a dashboard.

My part was the settings page and the backend work behind permission controls. I owned that work; the contract dashboard and the completed product belonged to the team's effort. My job connected the controls people could see with the permissions the system would allow.

Changing permissions needed to be straightforward for the people authorized to manage them. That ability also needed to stay limited to those people. The settings work had to address both needs together: make the permitted action easy to perform, while controlling who could perform it.

I worked across the interface and the Python/Flask backend to build that part of the tool.

By the end of the project, the team had delivered the behavior Mitsubishi requested. The client accepted the handoff and started using the tool to manage its contracts. I then moved to another agency assignment, Universal Orlando.

The assignment took me beyond a page's appearance and into the behavior behind its controls: who can act, and who decides that.

Edit Role dialog in a dark theme: a Select Role menu; an Access checkbox for Dashboards; Read, Edit and Download checkboxes (All or Assigned) for contracts data under Risk Score Database & Actions; and contracts-data Read checkboxes (All or Assigned) plus field Create and Edit checkboxes under Scoring Matrix
The Edit Role settings from my permission work: choose a role, then what it can open, read, edit and download. Screenshot from August 2022.

Case studies