You can’t change the extension on a document

We have made a change to the Card and Board Attachments feature to prevent users from changing the extension of a file they have already added: for example, a “.xlsx” file can’t be renamed as a “.docx” file.

We did this because changing the file type often had unpredictable consequences when a Team Member tried to upload an attachment.

This restriction applies to the most common file types, not all. Here’s how it works:

Image file attachment
Image file attachment

In the example above, an image has been added as an attachment to this card, and it has the .PNG file type/extension.

When you hover your mouse over any attachment, Kerika will show you the actions that are possible with that attachment, one of them being Rename.

Attachment options
Attachment options

If you select Rename, Kerika will make sure you only change the file name, not the file type/extension (.PNG in this example):

Renaming a document
Renaming a document

Whitelisting Kerika’s email notifications

In an effort to reduce the possibility of Kerika’s notifications ending up in your spam folder, we are making a bunch of changes: one that’s already gone into effect is that all notifications generated by Kerika — for example, when someone sends you a chat message, or you get your 6AM Task Summary email — will come from the same sender: notifications@mailer.kerika.com.

It would help us a lot if you whitelisted this sender email, either for your own personal email, or ideally for your organization’s entire domain.

Thanks.

 

We have improved our internal systems for managing users and accounts

This isn’t something that you will see, as a customer, but we have spent several months improving our internal systems for managing users, accounts, payments and invoices.

We used to do things in a very ad hoc way before, as we concentrated all our efforts on improving the Kerika app, but we realized earlier this year that we had reached the limits of ad hoc approaches and needed a lot more automation to handle growth.

Everything, pretty much, is now automated: our admin staff can quickly look up any any user or account, see which payments have been made (online or offline), and manage changes to accounts.

Using Google Drive without Google Docs

If you are using Kerika with Google, you don’t have to convert your documents to the Google Docs format in order to use Google Drive.

Google Docs Format Preference
Google Docs Format Preference

You can use this preference setting to ensure that your Microsoft Office documents, for example, are retained in MS Office format even while they they are stored and shared using Google Drive.

 

Consolidating multiple accounts within an organization

With the implementation of our shiny, new and fully automated billing system, it’s become a little more important for our customers to make sure that all the users within their organization are working in the right accounts — preferably, a single account.

Working in a single account, rather than a bunch of separate accounts, has advantages:

  1. It makes it much easier to pay for subscriptions: if all the Kerika users within a  department are working on boards owned by a single account, then only that account needs to purchase subscriptions.  This means less invoicing and payment stuff for you to worry about.
  2. It also ensures that all project assets — boards, documents, canvases, etc. — are owned by a single entity. And ideally this single entity would be a service account rather than an individual.  Many of our customers are using service accounts, set up using emails like kerika@example.com.

We have done a ton of improvements to the new user sign-up process to help guide people to working with their coworkers, using accounts that the coworkers have already set up, instead of creating new accounts.

But, there are still situations where an organization may find that, across all of its Kerika users, there are too many different accounts.  If this is the case for you, we can help: we can consolidate multiple accounts into a single account if you ask us.

This consolidation preserves all the existing boards, content, and project teams: it just changes the ownership of everything to be a single user ID.

Let us know if we can help you with this.