Account setup & administration

Your profile: name, photo, and password

Your profile is yours to edit — no admin role required. It lives at Settings → Your profile, and your name and photo are what teammates see on the Team board, on dashboards, and in the activity log.

Update your name and photo

1. Open Settings → Your profile.
2. Under Profile photo, choose Upload photo (or Replace). Pick a PNG or JPG — Pishik crops it to a square automatically. Remove clears it back to your initials.
3. Edit Your name — this is how you appear to teammates and in the activity log.
4. That's it — changes save on their own moments after you stop, and the status line confirms All changes saved. The one exception: your name can't be blank — the status line tells you the change is held until you enter one.

The Account row shows your sign-in email and role. Roles are managed by an admin under Settings → Team & users. Your sign-in email you can change yourself: press Change email… next to the address, type the new one and press Send code — Pishik emails a 6-digit code to the new address, so you have to be able to read that mailbox already. Enter the code, then confirm with your current password and an authenticator or backup code. An address that already has a Pishik account can't be used. Changing the email resets two-factor and signs out every session — you sign back in with the new address and re-pair your authenticator app.

Change your password

Every member can change their own password, in the same tab:

1. In Settings → Your profile, scroll to the Security section and press Change password.
2. Enter your current password, then a new password of at least 8 characters (your admin can require a longer minimum), and confirm it.
3. Press Change password.

The same Security section is where you manage two-factor authentication. Every Pishik account has it — there's no turning it on or off — so managing means Reset authenticator when you switch phones and New backup codes when you want to rotate your recovery set. The full walk-through — enrollment, backup codes, and recovery — lives in Set up two-factor authentication.

Common questions

• I forgot my current password. Use the password-reset link on the sign-in screen instead — see Can't sign in. An admin can also send you a reset from Team & users.
• My email or role is greyed out. Roles are admin-only — ask an admin under Team & users. Your sign-in email is self-serve: press Change email… in the Account row (it asks for a 6-digit code emailed to the new address — so that mailbox has to exist and reach you — plus your current password and an authenticator or backup code, and it won't accept an address that already has a Pishik account). Locked out of your second factor? Contact support.

Workspace defaults vs. your personal preferences

Pishik has two layers of settings, and it helps to know which is which:

• Workspace defaults apply to everyone who hasn't chosen otherwise. Admins set them at Settings → Preferences.
• Personal preferences are yours alone. Anyone can set them at Settings → Your profile, in the Personal preferences section. Where both exist, your setting wins for you and for the contracts you own.

Set your own preferences

1. Open Settings → Your profile and scroll to Personal preferences.
2. Pick a Default view, a Default contract type, and whether Pishik should email you when you're @mentioned. Each dropdown's first option is "Workspace default", which hands the choice back to your admin's setting.
3. Each choice saves the moment you make it — no save button — and applies to everything you do from then on. A reply-to address that isn't a valid email is the one thing held back: the status line says so until you fix or clear it.

Set the workspace defaults

You need: an admin or owner role. Open Settings → Preferences and set Default view, Default contract type, Email people when @mentioned, Overdue after, and Confirm before deleting. A pending review is flagged overdue on the board, dashboard, and flow map once it passes the Overdue after threshold without a decision.

In-app notifications for @mentions always appear regardless of the email setting — the toggle only controls whether Pishik also sends an email. The mention system itself is covered in Comments and @mentions.

Company branding: logo, name, and reply-to

You need: an admin or owner role. Branding lives at Settings → Company and shapes what reviewers see: your identity on every email and on the decision page they land on.

1. Company logo — press Upload logo and choose a PNG, JPG, or SVG (PNG with transparency works best). Pishik auto-resizes it for email. It appears in the app sidebar, on the sign-in screen, and at the top of every review email.
2. Company name — used in review emails, and shown in place of the logo when none is set.
3. Reply-to email — the workspace default. When a reviewer replies to a Pishik email, their reply lands here (for example, contracts@yourcompany.com).
4. Workspace URL is shown for reference — reviewer approve/reject links live at this address. It isn't editable here.

Whose reply-to wins

By default, replies go to your team's reply-to address — but each member can point replies to their own inbox from Settings → Your profile → Reply-to email. If you'd rather everyone use one company-wide address, turn on Require this reply-to for everyone in the Company tab. Members' personal reply-to fields then lock and show Set by admin.

Which email service actually delivers the mail is a separate topic, and not something you set per workspace; see How email delivery works.

Customize the emails Pishik sends

You need: an admin or owner role. Compose every email your workspace sends at Settings → Email content. A live preview on the right updates as you type, so you always see what a recipient will get.

Shared across every email

Three blocks appear on all outbound mail — review requests, reminders, and status updates alike:

• Email signature — signs off every email, above the clause.
• Confidentiality / privilege clause — fine print at the foot of every email.
• Email subject prefix — prepended to every subject (up to 40 characters) so recipients can filter their inbox, e.g. [Contract Review].

The signature and clause are rich text; Pishik sanitizes the HTML before sending.

Per-email-type messages

Below the shared blocks, three sub-tabs each carry their own message and preview:

• Reviewer → Reviewer instructions, shown in every review-request email and on the reviewer's decision page.
• Reminder → the Reminder message sent when a reviewer is nudged.
• Status → the Status message intro line, plus Default contents that decide how much a status email reveals.

Under Default contents you choose how much of the flow to show — Whole review flow, Where it is now, or General status only — and toggle individual details: Reviewer names, Approve / reject outcomes, Decision dates, and What's coming up next. These are defaults; you can override any of them per send from a contract — handy for hiding reviewer names from an external party. See Send a status update.

1. Edit any field; watch the Live preview update.
2. Everything saves on its own as you go — the header shows Saving… while you type and settles to All changes saved a moment after you stop. Switching tabs never loses an edit.

Contract types and reviewer departments

You need: an admin or owner role. Two small lists keep your workspace tidy: the contract types people pick from, and the departments your reviewers are grouped by.

Contract types

Types appear in the Type dropdown when someone creates a contract. Manage them at Settings → Contract types:

1. Add a type by typing a name (e.g. Lease, Partnership) and pressing Add. Duplicates are rejected.
2. Reorder with the move-up / move-down arrows — the order here is the order of the dropdown.
3. Remove a type with the trash icon.

Reviewer departments

Departments group your reviewer book. Manage them from Settings → Reviewers → Manage departments:

1. Add a department by name.
2. Rename one to update it everywhere — every reviewer in it moves with the change.
3. Merge by renaming a department onto a name that already exists: Pishik asks to confirm, then moves all its reviewers into the target.
4. Delete a department; its reviewers become Unassigned (nothing is lost).

Every change is recorded in a Recent changes log inside the dialog. Unassigned is a reserved name — you can't create a department called that. Adding reviewers themselves is covered in Add reviewers to your reviewer book.

Configure automatic reviewer reminders

Pishik can chase reviewers who haven't decided yet, so you don't have to. There are two places to set it — and, like other preferences, personal settings win for the contracts you own:

• Workspace default (admin): Settings → Preferences → Automatic reminders.
• Your own schedule (anyone): Settings → Your profile → Personal preferences → Automatic reminders.

Reminders always go out on the contract owner's schedule.

1. Turn Automatic reminders on.
2. Set Remind every N days — anywhere from 1 to 30.
3. Set the cap: up to N reminders — from 1 to 10. This is the total number of automatic reminders each reviewer receives for a review; manual nudges don't count against it.
4. Choose Send them at a time of day. Reminders go out on your local clock — Pishik records your timezone whenever you adjust the reminder settings.

What automatic reminders won't do

• They only chase pending reviewers on contracts that are In Review with an active stage. A decided or draft contract is left alone.
• They stop at your cap, and never double up on a reviewer within the same day.
• The 45-day cutoff: once a review has gone 45 days without a single send or reminder, automatic reminders stop for it. Each send resets that clock, so an active cadence is never cut off — the cutoff only catches reviews nothing has touched in 45 days. A review that quiet needs a human decision — resend it, reassign it, or revise & restart — not another robo-nudge. See Remind and resend and Handle a rejection.

Workspace limits: contracts, outbox, and saved paths

A Pishik workspace runs inside a few generous guardrails. You'll almost never meet them, but here they are in plain numbers:

A couple of things worth knowing:

• The 5,000-contract cap counts every contract in the workspace — active and archived alike. Archiving a finished contract to the Repository tidies your board but doesn't free a slot; to reclaim one you'd delete the contract.
• The 2.5 MB size limit is metadata only — share links, workflow state, notes, and comments. Your actual documents never count against it, because they stay in your own storage (the share-link model).
• These are not the seat limit. Reviewers are unlimited and free; seats apply only to people who sign in, and are capped by your plan — see Seats and reviewers.