Web Developer Internship

The Admin Dashboard is the first thing admins see after logging in. We designed it as a quick overview of everything important: how many items are available, how many have been borrowed, which divisions are most active, and any recent borrowing activity. From this single page, admins can jump straight into managing divisions, categories, items, users, and borrowing requests. The goal is to reduce “clicks” — admins shouldn’t have to dig through menus just to see what’s going on.

In a government office, assets are usually tied to divisions (e.g., IT, Finance, Services). Our app includes a Divisions Management module so admins can clearly define where each item belongs. Admins can add new divisions, edit existing ones, or deactivate divisions that are no longer used. This structure then becomes the backbone for items and borrowing, because every item is assigned to a division.

To avoid a messy list of random items, we introduced two important concepts: Categories and Locations. Categories help classify items by type, such as laptops, printers, furniture, or networking equipment. Locations represent where those items physically live: specific rooms, floors, or offices. By combining divisions, categories, and locations, admins can organize assets in a way that makes sense both logically and physically.

The Items Page is where the actual assets live in the system. Each item has details like name, code, category, division, location, and status. Because the number of assets can grow large, we added a search feature to help admins quickly find what they need. They can search by item name, code, division, or other key fields. Combined with filters, this makes it much easier to manage a growing inventory.

We noticed that many offices still love working with Excel for reporting and documentation, so we added a Export to Excel feature. With just one click, admins can export the current list of items (or other relevant data) into an Excel file. We wanted this to feel straightforward: no complicated setup, just click and download.

Not everyone should have the same level of access. That’s why we built a User Management module for admins. From here, admins can create and manage user accounts, assign roles (Admin or Employee), and control access to different parts of the system. This separation of roles keeps the system more secure and ensures that only authorized people can approve asset movements.

Every time an asset is borrowed or returned, it leaves a “trail.” The Borrowing Log is where that trail is recorded. This page lists all borrowing activities: who borrowed what, from which division, when they borrowed it, and when it was returned. This is crucial for accountability and helps prevent items from being “lost” or forgotten.

Before users can access anything, they start at the Landing Page. From here, employees can log into the system using their account. We kept the landing and login screens simple and focused with a clear login form and a short introduction.

Once an employee logs in, they are taken to the Employee Dashboard. This is their “home base” for everything related to borrowing assets. The idea is to make it very clear what they are allowed to borrow and what the current status of each request is — without needing to contact the admin every time.

One of the core features is the borrowing workflow. It follows a strict path: 1) Employee submits request, 2) Admin reviews (Approve/Reject), 3) If approved, item becomes borrowable, 4) Employee borrows item (system updates to 'borrowed'), 5) Item returned (system updates to 'returned'). This prevents unauthorized usage and keeps asset movement transparent.

This internship project at DPMPTSP Kota Bandung was more than just a coding exercise. It was a chance to understand real office workflows and translate them into a functioning system. Working together with my team and mentor, we learned how to design features that fit how people actually manage assets day to day.