The Day You Can't Remember Which Email You Used
You listed a laptop repair service on Tap.az. Then again on Lalafo.az. Then on TopElan.az because a customer mentioned they found suppliers there. Each platform got a slightly different username — one your email, one a phone number, one a handle. Passwords were set to "something memorable" at the time, which now means nothing because three months have passed and you're staring at a login prompt with no idea what you entered.
The locked-out scenario is merely the most visible failure. The deeper problem is operational drift: you stop using platforms not because they're unproductive but because the friction of accessing them exceeds the perceived benefit. You lose visibility into where your listings are active. You miss messages from potential customers because you forgot you even had an account on UcuzTap.az. Your digital storefront becomes a scattered collection of half-remembered commitments.
The Fields That Create Operational Clarity
The core of this template is the Saytın növü (site type) field: classified ads, email, or social network. That three-way classification is not cosmetic. It determines how you interact with the account. Ad platforms need regular listing refreshes to stay ranked. Email accounts need periodic inbox reviews. Social accounts need engagement. Grouping by type means a filtered view gives you your active classified platforms in one pass, your email accounts in another — so you can run through a maintenance round without context-switching.
Identifikasiya tipi — the boolean identification type field — distinguishes between email-based logins and phone-number-based logins. When Tap.az locks you out for suspicious activity and sends a recovery code, it matters enormously whether that code goes to a phone you're holding or an email address you rarely check. Having this field populated means you know, before you hit the recovery workflow, which channel to watch.
Yenilənmə tarixi — the last-updated datetime — is underrated. Passwords have a practical decay rate in terms of security hygiene. If you sort your credential records by this field and see accounts that haven't been touched in eighteen months, those are candidates for a password rotation sweep. Without the field, you have no way to audit staleness across your portfolio of platform accounts without opening each one individually.
The Populyarlığı (popularity/rating) field at five stars is for recording which platforms actually convert — which ones generate inquiries versus which ones sit dormant. After three months of tracking, a two-star rating on a platform you're actively maintaining is a clear signal to deprioritize it. You don't need analytics dashboards for this. You need a rating field and honest use.
What a 40-Account Credential Database Looks Like in Practice
When you're running an electronics repair and parts business across every major Azerbaijani marketplace — TapSat.az, Hand2Hand.az, Mojo.az, Seller.az, and a dozen others — the count gets to forty accounts faster than expected. Social presences, business email addresses, dedicated seller accounts on platforms with separate login systems for buyers and sellers: they multiply.
At that scale, the EDİLƏCƏKLƏR (to-do list) field on each credential record becomes a task queue. "Update laptop repair listing with new pricing" lives on the Tap.az record. "Respond to pending inquiry" sits on the Lalafo.az record. The credential record is no longer just authentication data — it's a per-platform action log that keeps account maintenance from falling through the cracks.
The Kateqoriya seçimləri tree field allows hierarchical classification within the record set — useful when the same platform has sub-accounts or when you want to distinguish between personal and business-use accounts on the same service.
The SKRİPT file attachment and HTML JavaScript field are the advanced layer. You can attach automation scripts directly to a platform's credential record — a scraper, a bulk-listing tool, an API integration — and the script lives co-located with the credentials it requires. When you update the password, you're in the same record as the script that uses it.