Merchant Records
Display onlyShows the total number of current merchant records that have not been soft-deleted.
Data shown: Merchants enter this count when they are created or imported. A merchant leaves the count only when it is soft-deleted.
Taboo CRM
Modern CRM operations for customers, workflows, and payments.
Welcome back
Taboo CRM
Account Access
Taboo CRM
Secure Link
Taboo CRM
Signed in as
Search results will appear on the left.
My Profile
The Home page combines work assigned to you with operational information from across the CRM. What you see can vary by your active role, merchant assignments, and the selected followup scope.
Use the calendar and work lists first, then review alerts and pipeline counts. The performance containers provide context and do not require daily action.
Shows the total number of current merchant records that have not been soft-deleted.
Data shown: Merchants enter this count when they are created or imported. A merchant leaves the count only when it is soft-deleted.
Shows active merchant and user followups whose scheduled time has passed.
Data shown: Followups are created from merchant and user records. The total follows the My Followups or All Followups scope selected below.
Shows active merchant and user followups scheduled from now through the next 14 days.
Data shown: The total is calculated from saved followup dates and follows the selected followup scope.
Shows the number of auditable CRM events recorded during the last 14 days.
Data shown: The application creates audit events automatically when tracked actions occur, such as merchant changes, workflow actions, and administrative updates.
Displays up to 25 active merchant and user followups that are overdue or due within 14 days. Overdue items are shown first.
How to use it: Admin users can switch between My Followups and All Followups. Use the month arrows and calendar days to view a specific date. Select Show upcoming to return to the rolling work list. Open a row to view its merchant or user, or use Reschedule and Complete directly from Home.
Data shown: Followups are created and assigned on merchant and user records. Calendar markings combine the merchant and user followups visible under the selected scope.
Lists appointments for the date selected on the Home calendar. The default date is today.
How to use it: Select an appointment to open the merchant. Create or change appointments from the merchant's Appointments tab.
Data shown: Appointments are created on merchant records and appear when you are assigned to the appointment as an agent, manager, ISO, processor, or owner. All Followups allows Admin users to view the broader schedule.
Displays active company messages intended for your current role.
Data shown: Administrators create announcements under Admin > Operations > News & Announcements and control their audience and active dates.
Shows the eight merchants with the most recent local activity.
How to use it: Select a row to open the merchant Overview.
Data shown: A merchant appears after a local save or an auditable merchant action. The date reflects the newest of those recorded activities, not the original import date.
Lists merchants whose banner alert is currently enabled, with the merchant name, status, and alert date.
How to use it: Select an alert to open the merchant Overview and review or change the alert.
Data shown: Alerts are created when an authorized operator enables Alert On in the merchant Overview.
Compares your pipeline with the Total-Apps pipeline for Lead, Pre-app, Incomplete, Pending, Processing, and Integrating merchants.
How to use it: Select any nonzero count to open Merchant Search filtered to that status.
Data shown: My Pipeline counts merchants assigned to you as manager. Total-Apps Pipeline counts all current merchants in each displayed status. On Hold work due today is included with your Pre-app workload.
Shows your Accounts Received, Submitted, Approved, and Closed totals for the previous calendar month.
Data shown: Totals are calculated from recorded merchant status changes and merchants assigned to your user account. Missing activity is displayed as zero.
Shows team account activity for the three previous calendar months.
Data shown: Received, Submitted, Approved, Closed, and Processing totals are calculated from merchant status history. A dash means that a metric is not currently populated.
Shows how many current merchants are assigned to you under each assignment type.
Data shown: Counts come from the Manager, Processor, Agent, ISO, Referral, and Biz Dev assignments saved on merchant records. Only assignment types with merchants are listed.
These charts are reference-only views of data already summarized elsewhere on Home. They do not change records.
Visualizes your Received, Submitted, Approved, and Closed counts for the previous month.
Data shown: Uses the same status-history totals as the personal performance container.
Compares team Received, Submitted, Approved, and Closed totals across the previous three months.
Data shown: Each colored series is calculated from recorded merchant status transitions.
Compares the number of processing accounts across the previous three months.
Data shown: Counts come from merchant status-history activity for Processing accounts.
Shows the relative size of the current Total-Apps pipeline by application status.
Data shown: Uses the same current merchant counts displayed in the Total-Apps Pipeline column.
The Users page is the administrative workspace for finding user accounts, creating users, managing access, and maintaining user-related records. Only Admin users can open the Users page or another user's record.
Every signed-in user can open their own profile and password-reset form by selecting the avatar circle in the upper-right corner. This self-service profile does not provide access to the Users workspace.
Finds users by name, username, email, or company. Role and status filters can narrow the results to Active, Pending Approval, Inactive, or all users.
How to use it: Enter any known information, choose optional filters, and select Search. Results remain hidden until a search is performed.
Data shown: Search reads current user profiles, assigned roles, and account status from the CRM database.
Each result shows the user's name, status, email or username, User ID, and assigned roles.
How to use it: Select a result to open the user record. Use Previous and Next to move through large result sets.
Data shown: Status reflects whether the account is active, awaiting approval, or disabled. Disabled users cannot sign in.
Exports the users matching the current search and filters in CSV or Excel format.
How to use it: Run a search, select Download, and choose CSV or XLSX.
Data shown: The export uses the same query and filters as the visible search results, without limiting the file to the current page.
Creates a user with a required name, unique login username, email, phone, and at least one role. Company and active status can also be set.
How to use it: Leave Send password setup email selected to queue a single-use setup link. Clear it only when an initial password of at least 10 characters will be entered directly.
Data shown: A new record receives its User ID from the database. The username is the value used at login.
Shows the selected user's name, username, email, phone, company, roles, User ID, and account status.
Data shown: Values come from the saved user profile and role assignments. Profile changes are made in the administrative sections below.
Updates email, phone, company, and whether the account is active.
How to use it: Clear Active to disable an account and prevent future logins. Select Save User after making changes.
Data shown: The status badge at the top of the record updates from the saved account status.
Controls which roles the user can select during sign-in and which role-based permissions apply.
How to use it: Select all roles the user is authorized to perform, then save the assignments. Detailed report and merchant-tab access may also be controlled by administrative permission settings.
Data shown: Available roles come from the current role catalog; checked roles are the user's saved assignments.
Maintains applicable Manager, ISO, Processor, or Referral reporting relationships and lists merchants and users connected to the selected account.
How to use it: Save parent relationships when they apply. Select linked merchant names, MIDs, or usernames to open the related record; use the pagers for longer lists.
Data shown: Relationship choices come from active users with the required role. Lists are built from saved user relationships and merchant assignments.
Lets an Admin review the application as the selected active user and role without granting write access during the preview.
How to use it: Choose an assigned role and begin the temporary session. Exit the preview to return to normal Admin access.
Data shown: The preview uses the selected user's assignments and permissions. Starting and ending the session are audited.
Appears for accounts awaiting administrative approval.
How to use it: Review the profile and roles, then approve the user to activate the account and queue a password setup email.
Data shown: This section appears only while the account has Pending Approval status.
Admin Password Reset sets a new password directly. Password Setup Email queues a single-use link so the user can choose a password privately.
How to use it: Prefer the setup email when the user can receive email. Use direct reset only when operationally necessary; passwords must meet the displayed minimum length.
Data shown: Password change and setup-email events are recorded in administrative history without storing the password in the audit detail.
Appears for users assigned the Referral role and manages their private referral-agreement link and agreement history.
How to use it: Send a new expiring agreement when needed. A new request invalidates an earlier pending request.
Data shown: History shows saved sends, expiration, and completion information for the selected referral user.
Adds and maintains individual or department contacts associated with the user, including title, email, work phone, cell phone, fax, and notes.
Data shown: Contacts are separate child records created and updated from this tab. Deletes require confirmation.
Adds and maintains labeled addresses with company, website, street, city, state, postal code, country, phone, and fax details.
Data shown: Addresses are separate child records saved to the selected user and protected against overwriting a newer edit.
Maintains the user's bank name, business or personal account type, ABA routing number, and account number.
How to use it: Sensitive values are masked by default. Use the eye button only when the full value must be reviewed or replaced.
Data shown: Banking values come from the selected user's saved banking profile. Sensitive-value access and changes are auditable.
Uploads, downloads, and deletes private documents associated with the user.
How to use it: Enter a document name, choose a category and file, then upload. Files must meet the displayed size and type rules and pass a security scan before storage.
Data shown: The list shows stored document metadata, uploader, date, file size, and whether the underlying file is available.
Adds, edits, and deletes administrative notes about the selected user. Notes are shown 25 per page with the author and timestamp.
Data shown: Notes are created by authorized operators on this tab and retained in the user's history according to application audit rules.
Creates dated work reminders, assigns them to an eligible user, and supports saving, completing, or reopening existing followups.
How to use it: Choose the responsible user, date and time, and note. Open followups can appear in the assigned user's Home calendar and work list.
Data shown: Followups are saved against this user record and listed 25 per page, including their current completion state.
Provides a paginated timeline of recorded activity associated with the user, including the event title, time, actor, and available detail.
Data shown: Entries are created automatically by audited user operations and imported user history. This tab does not change records.
Every signed-in user can select the avatar circle in the upper-right corner to review their own name, username, email, phone, company, roles, User ID, and status.
How to use it: This is the correct path for non-Admin users to view their own profile because the top-level Users menu is intentionally hidden from them.
Data shown: The modal loads only the currently authenticated user's profile.
Allows a signed-in user to change their own password by supplying the current password and confirming a new password.
How to use it: Open the avatar profile, enter the current password, then enter and confirm the new password.
Data shown: A successful change updates the current account and records a password-change audit event without exposing the password.
| Sr. No. | Status Title | Status Description |
|---|---|---|
| Loading status descriptions... | ||
Uploads are scanned and staged for review. No processing or commission data changes until an error-free batch is applied.
CID-based Agent, ISO, Referral, and Total-Apps splits are validated and staged as one atomic batch.
Canonical login usernames are matched to active users with the corresponding role. Any invalid row rejects the entire batch.
These source notes reference UIDs that no longer exist. Map each note to a verified user or discard it with a documented reason.
These source banking profiles reference UIDs that no longer exist. Sensitive values remain masked. Map only to a verified user without an existing banking profile, or discard the record with a documented reason.
These records either reference a UID that no longer exists or a source file that was not present in the copied archive. Recoverable orphan files are scanned, hashed, and copied into private storage only after they are mapped to a verified user.
Search results will appear on the left.
Create the merchant with its required profile and assignments.